x402basequality 0.25

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

Price
0.02 USDC / call
Protocol
x402
Verified
no

What it does

This endpoint at lowpaymentfee.com provides a KYC (Know Your Customer) verification service accessible at `/api/v1/kyc/verifications/74`. It is part of a broader platform offering dozens of pay-per-call APIs spanning data analytics, AI/ML inference, finance, crypto, and utility services. All endpoints on the platform use the x402 payment protocol, settling in USDC on the Base network.

The specific endpoint probed (`/api/v1/kyc/verifications/74`) returns a live 402 challenge requesting payment of up to 20,000 base units of USDC (0.02 USD) per call. The platform advertises a flat $0.02/request pricing model with no API keys, no rate limits, and instant access. The endpoint accepts HTTP POST requests and returns `application/json` responses.

Documentation is extremely sparse — the docs, pricing, API, and README pages all render only a "Connect wallet" prompt with no substantive content. There is no OpenAPI schema, no request/response examples, and no description of what input the KYC verification endpoint expects or what it returns. The resource path includes a numeric ID (`74`), but it is unclear whether this refers to a specific verification record, a verification type, or something else. Without documentation, the actual functionality and required request body remain unknown.

Capabilities

kyc-verificationx402-paymentusdc-settlementbase-networkper-call-pricingjson-responsehttp-post

Use cases

  • Performing KYC identity verification checks on demand
  • Integrating compliance verification into onboarding flows
  • Agent-driven identity checks with micropayment settlement

Fit

Best for

  • Developers needing pay-per-call KYC without API key management
  • Agents that can settle USDC payments on Base via x402
  • Low-volume or sporadic identity verification needs

Not for

  • High-volume KYC pipelines requiring documented SLAs and schemas
  • Users who need detailed documentation or integration guides before adopting
  • Fiat-only payment environments with no crypto wallet capability

Quick start

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

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.25/ 1.00

The endpoint is live and returns a valid x402 challenge, but there is zero documentation on request format, response schema, or what the KYC verification actually does. No OpenAPI spec, no examples, and all doc 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.
  • No OpenAPI or request/response schema provided; the required input body is completely unknown.
  • The path '/api/v1/kyc/verifications/74' includes a hardcoded numeric ID whose meaning is unclear.
  • KYC/identity verification is a regulated category — no information on data handling, compliance certifications, or privacy policy is available.
  • The platform homepage does not list any KYC endpoints among its advertised APIs, raising questions about whether this endpoint is production-ready or experimental.

Citations

Provenance

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

Agent access