x402basequality 0.30

KYC verification endpoint on Base, pay-per-call via x402 with USDC.

Price
0.02 USDC / call
Protocol
x402
Verified
no
Endpoint
https://lowpaymentfee.com/api/v1/kyc/verifications/71

What it does

This endpoint at lowpaymentfee.com provides a KYC (Know Your Customer) verification service accessible via the x402 payment protocol. The specific resource `/api/v1/kyc/verifications/71` accepts POST requests and charges up to $0.02 per call in USDC on the Base network. No API keys or rate limits are required — callers simply attach an x402 payment header to each request.

The hosting site lowpaymentfee.com offers a broad catalog of pay-per-request APIs spanning data analytics, AI/ML inference, finance/Web3 data, and infrastructure utilities, all priced at $0.02 per request. However, the specific KYC verification endpoint's input schema, required POST body fields, and response format are not documented in any crawled material. The docs, pricing, and API pages all resolve to a minimal "Connect wallet" prompt with no further detail. Because of this, the exact capabilities of the KYC verification (e.g., what identity documents or data it accepts, what verification checks it performs, what the response payload looks like) remain unknown.

Payment settles on Base using USDC (contract 0x8335…2913) with a maximum amount of 20,000 base units, which equals $0.02 (USDC uses 6 decimals). The payee address is 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3. The endpoint is live and returns a valid x402 challenge.

Capabilities

kyc-verificationx402-paymentusdc-basepay-per-requestno-api-key

Use cases

  • —Verifying user identity as part of onboarding flows
  • —Compliance checks for financial or Web3 applications
  • —Automated KYC screening in agent-driven workflows

Fit

Best for

  • —Developers needing pay-per-call KYC without subscription commitments
  • —Agent workflows that require on-demand identity verification
  • —Web3 applications settling micropayments on Base

Not for

  • —Bulk KYC processing where batch pricing is needed (no volume discounts documented)
  • —Use cases requiring detailed documentation of verification methods and supported ID types

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/kyc/verifications/71 \
  -H "Content-Type: application/json" \
  -H "X-PAYMENT: <x402-payment-token>" \
  -d '{}'

Endpoint

URLhttps://lowpaymentfee.com/api/v1/kyc/verifications/71
Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.30/ 1.00

The endpoint is live and returns a valid x402 challenge, but there is zero documentation on request/response schemas, required fields, or what the KYC verification actually checks. Docs pages are empty. This is effectively a stub listing.

Warnings

  • —No documentation available — docs, pricing, API, and README pages all show only 'Connect wallet' with no content.
  • —Request body schema for the KYC verification POST is completely unknown.
  • —Response format and fields are undocumented.
  • —It is unclear what identity data or documents the endpoint accepts or what verification checks it performs.
  • —KYC/identity verification is a regulated category — callers should verify the provider's compliance credentials independently.
  • —The endpoint path includes a numeric ID (71) whose meaning is unexplained.

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-19 05:04:09Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-18
Last seen2026-04-22

Agent access

JSONhttps://clawmart.sh/api/listings/nkPeeZ
KYC verification endpoint on Base, pay-per-call via x402 with USDC. — Clawmart · Clawmart