KYC verification endpoint on Base, paid per-call via x402 with USDC.
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/12` 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 request format and the structure of the verification response remain unknown.
The endpoint is live: it returns a proper x402 version-1 challenge with payment details (USDC on Base, payTo address 0x1A2B…85F3, max amount 20000 base units = $0.02). The outputSchema confirms it is a discoverable HTTP POST endpoint. Without documentation on what fields to submit or what a successful verification response looks like, agents will need to experiment or obtain documentation out-of-band.
Capabilities
Use cases
- —Verifying customer identity as part of onboarding flows
- —Programmatic KYC checks for fintech or Web3 applications
- —Agent-driven compliance verification without API key management
- —On-demand identity verification with per-call USDC payment
Fit
Best for
- —Developers needing pay-per-call KYC without subscription commitments
- —AI agents that can settle payments on Base via x402
- —Web3 applications requiring inline identity verification
Not for
- —Bulk KYC processing where per-call pricing is inefficient
- —Use cases requiring detailed documentation or SLA guarantees
- —Applications that cannot transact in USDC on the Base network
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/kyc/verifications/12 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-token>" \
-d '{}'Endpoint
Quality
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 stubs. The listing is effectively a stub with only pricing and liveness confirmed.
Warnings
- —No documentation available — request body fields and response schema are completely unknown
- —The endpoint path includes a hardcoded ID (/12) whose meaning is unclear — it may be a specific verification type or a placeholder
- —Docs, pricing, and API pages all render only a 'Connect wallet' prompt with no usable content
- —KYC/identity verification is a regulated category — verify the provider's compliance posture before relying on this in production
Citations
- —The endpoint returns a valid x402 challenge with maxAmountRequired of 20000 base units of USDC on Basehttps://lowpaymentfee.com/api/v1/kyc/verifications/12
- —All APIs on the site are priced at $0.02 per request with no API keys, no rate limits, and instant access on the Base networkhttps://lowpaymentfee.com
- —USDC asset address 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Base networkhttps://lowpaymentfee.com/api/v1/kyc/verifications/12