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

The parent site lowpaymentfee.com hosts a broad 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 specific KYC verification endpoint's input schema, required POST body fields, and response format are not documented in any crawled page. 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 (what data it accepts, what checks it performs, what it returns) remain unknown.

The endpoint is confirmed live: it returns a valid x402 challenge (HTTP 402) with version 1, accepting USDC (contract 0x8335…) on Base, paying to address 0x1A2B…85F3, with a 300-second timeout. The listed maxAmountRequired of 20000 base units equals $0.02 given USDC's 6 decimals.

Capabilities

kyc-verificationx402-paymentusdc-settlementbase-networkper-call-pricingno-api-key

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 identity verification to Web3 or DeFi applications

Fit

Best for

  • Developers needing pay-per-call KYC without subscription commitments
  • AI agents that can settle payments via x402 on Base
  • Web3 applications requiring inline identity verification

Not for

  • Use cases requiring documented input/output schemas before integration
  • High-volume KYC pipelines needing bulk pricing or SLAs
  • Regulated environments that require vendor compliance certifications

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/kyc/verifications/77 \
  -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 the KYC verification's input fields, response format, or what checks it actually performs. The docs/pricing/API pages are all empty beyond a wallet-connect prompt. This is effectively a stub listing.

Warnings

  • No documentation available for the KYC verification endpoint — required POST body fields and response schema are completely unknown.
  • The path includes a hardcoded ID (/verifications/77) which may indicate a specific verification record rather than a general-purpose endpoint.
  • No OpenAPI spec, no AI plugin manifest, and no robots.txt or agents.txt found.
  • KYC/identity verification is a regulated category — no compliance certifications or data handling policies are documented.
  • Docs, pricing, API, and README pages all return only a 'Connect wallet' prompt with no substantive content.

Citations

Provenance

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

Agent access

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