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 at `/api/v1/kyc/verifications/72`. It uses the x402 payment protocol, accepting USDC on the Base network. The price per request is $0.02 (20,000 base units of USDC with 6 decimals). No API keys or rate limits are required — callers simply attach an X-PAYMENT header with a valid x402 payment proof to access the resource.
The broader lowpaymentfee.com platform offers a range of pay-per-call APIs spanning data analytics, AI/ML inference (sentiment analysis, summarization, classification, embeddings), finance and crypto market data, and infrastructure utilities (geocoding, validation, conversion, generation). All endpoints share the same $0.02/request pricing model and settle on the Base network using USDC. The specific endpoint listed here (`/api/v1/kyc/verifications/72`) appears to be a KYC verification resource, though detailed documentation on its request/response schema is not available — the docs, pricing, and API pages behind the site require a wallet connection and yielded no substantive content during crawl.
The endpoint is confirmed live, returning a proper 402 challenge with x402 version 1. The payment is directed to address `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3` using the USDC contract `0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913` on Base. The timeout for payment settlement is 300 seconds.
Capabilities
Use cases
- —Verifying customer identity as part of onboarding flows
- —Compliance checks for financial or crypto applications
- —Automated KYC screening without managing API keys or subscriptions
- —Agent-driven identity verification with micropayment settlement
Fit
Best for
- —Developers needing on-demand KYC checks without subscription commitments
- —Crypto-native applications that can pay with USDC on Base
- —Agents or automated workflows requiring pay-per-call identity verification
Not for
- —Users who need detailed documentation or schema guarantees before integrating
- —High-volume KYC pipelines where bulk pricing would be more cost-effective
- —Applications that cannot settle payments in USDC on the Base network
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/kyc/verifications/72 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402_payment_proof>" \
-d '{}'Endpoint
Quality
The endpoint is confirmed live with a valid 402 challenge, but there is no OpenAPI schema, no request/response documentation, and no examples. The docs pages require wallet connection and returned no content. The specific purpose of the '/72' resource ID is unclear. Effectively a stub listing.
Warnings
- —No request or response schema available — the endpoint's expected input and output are unknown.
- —Documentation pages require wallet connection and provided no usable content during crawl.
- —The resource path includes a numeric ID (/72) whose meaning is undocumented — it may be a specific verification record rather than a general-purpose endpoint.
- —KYC/identity verification is a regulated category; verify the provider's compliance posture before relying on this in production.
Citations
- —The endpoint returns a 402 challenge with x402 version 1, accepting USDC on Base with maxAmountRequired of 20000 base units.https://lowpaymentfee.com/api/v1/kyc/verifications/72
- —All endpoints on the platform are priced at $0.02 per request with no API keys, no rate limits, and instant access on the Base network.https://lowpaymentfee.com
- —USDC contract address is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 and payTo is 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3.https://lowpaymentfee.com/api/v1/kyc/verifications/72