x402basequality 0.30

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

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 via the x402 payment protocol. The specific path `/api/v1/kyc/verifications/20` accepts POST requests and charges $0.02 per call in USDC on the Base network. Payment is handled inline via the x402 header — no API keys, accounts, or rate limits are required.

The provider, lowpaymentfee.com, hosts a broader catalog of pay-per-call APIs spanning data analytics, AI/ML inference, finance/Web3 data, and infrastructure utilities, all priced at $0.02 per request. However, the KYC verification endpoint is not listed on the provider's public landing page, so its exact input schema and response format are undocumented in the crawled material. The x402 challenge confirms the endpoint is live and accepts POST with `application/json` content type, settling payments to address `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3` using USDC (`0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913`) on Base.

Because no OpenAPI spec, request/response examples, or detailed documentation were found for this specific endpoint, the exact fields required in the POST body and the structure of the verification response remain unknown. Users should expect to experiment or contact the provider for integration details.

Capabilities

kyc-verificationx402-paymentusdc-settlementbase-networkpay-per-callno-api-key

Use cases

  • Verifying customer identity as part of onboarding flows
  • Compliance checks for financial or Web3 applications
  • Automated KYC screening triggered by agent workflows
  • On-demand identity verification without subscription commitments

Fit

Best for

  • Developers needing low-cost, no-signup KYC verification
  • Agent-based workflows requiring inline crypto-paid identity checks
  • Applications on Base network that want native USDC settlement

Not for

  • Users who need detailed documentation or guaranteed SLAs before integrating
  • Bulk KYC processing where per-call pricing may not be cost-effective
  • Workflows requiring fiat-only payment rails

Quick start

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

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.30/ 1.00

The x402 challenge confirms the endpoint is live and priced, but there is no documentation, no OpenAPI schema, no request/response examples, and the KYC endpoint is not even listed on the provider's own landing page. Effectively a stub with verified liveness.

Warnings

  • KYC verification endpoint is not listed on the provider's public landing page — may be experimental or unlisted.
  • No request body schema or response schema available; integration requires guesswork or provider contact.
  • KYC/identity verification is a regulated category — verify the provider's compliance posture before relying on results.
  • Documentation pages (/docs, /api, /pricing, /README) returned only a 'Connect wallet' prompt with no useful content.

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