x402basequality 0.30

KYC verification endpoint on Base, pay-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/35`. It uses the x402 payment protocol, settling on the Base network in USDC. The endpoint accepts POST requests and returns JSON responses. The x402 challenge advertises a maximum amount of 20,000 base units of USDC (6 decimals), which equals $0.02 per request.

The broader lowpaymentfee.com platform hosts a variety of pay-per-call APIs spanning data analytics, AI/ML inference (sentiment analysis, summarization, classification, embeddings), finance and crypto data (price feeds, exchange rates, gas estimates), and infrastructure utilities (geocoding, validation, conversion). All endpoints share the same $0.02/request pricing model with no API keys, no rate limits, and no commitments required — payment is handled entirely through the x402 protocol.

The specific KYC verification endpoint's input schema and expected request body are not documented in the crawled material. The path includes an ID segment (`/35`), suggesting it may operate on a specific verification resource. No OpenAPI spec, detailed docs, or example payloads were found; the docs, pricing, and API pages all returned only a "Connect wallet" prompt with no substantive content.

Capabilities

kyc-verificationx402-paymentusdc-settlementbase-networkpay-per-callno-api-keyjson-response

Use cases

  • Verifying customer identity as part of onboarding flows
  • Performing KYC checks without managing API keys or subscriptions
  • Integrating compliance verification into agent-driven workflows
  • Adding pay-per-use identity verification to Web3 applications

Fit

Best for

  • Developers needing low-friction, pay-per-call KYC checks
  • Agent workflows that settle payments on Base with USDC
  • Projects that want to avoid API key management for compliance endpoints

Not for

  • Bulk KYC processing where per-call pricing is inefficient
  • Use cases requiring detailed documentation or SLA guarantees
  • Teams that cannot settle payments in USDC on the Base network

Quick start

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

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.30/ 1.00

The endpoint is live (returns a valid x402 402 challenge), but there is no OpenAPI spec, no request/response schema documentation, no example payloads, and the docs pages are empty. The specific purpose of the KYC verification endpoint and its expected inputs are entirely undocumented, making this effectively a stub listing.

Warnings

  • No OpenAPI spec or request/response schema available for this endpoint.
  • Documentation pages (/docs, /api, /pricing, /README) returned no substantive content — only a 'Connect wallet' prompt.
  • The purpose and required input fields for /api/v1/kyc/verifications/35 are unknown; the path segment '35' is unexplained.
  • KYC/identity verification is a regulated category — verify the provider's compliance posture before relying on this in production.

Citations

Provenance

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

Agent access