KYC verification endpoint on Base, pay-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/98` accepts POST requests and charges up to $0.02 per call in USDC on the Base network. No API keys or rate limits are required — callers simply attach an x402 payment header to each request.
The hosting site lowpaymentfee.com offers a broad catalog of pay-per-request 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 the crawled material. The docs, pricing, and API pages all resolve to a minimal "Connect wallet" prompt with no further detail. Because of this, the exact capabilities and expected request/response payloads for the KYC verification call remain unclear.
The endpoint is confirmed live: it returns a proper x402 version-1 challenge with USDC (contract 0x8335…) on Base, a payTo address, and a 300-second timeout. The payment scheme is "exact," meaning the full maxAmountRequired of 20,000 base units (i.e., $0.02 given USDC's 6 decimals) is charged per call.
Capabilities
Use cases
- —Verifying customer identity as part of onboarding flows
- —Automated KYC checks for fintech or Web3 applications
- —Compliance screening triggered by agent workflows
- —On-demand identity verification without API key management
Fit
Best for
- —Developers needing pay-per-call KYC without subscription commitments
- —Agent-driven compliance workflows that settle in USDC on Base
- —Prototyping identity verification integrations with minimal setup
Not for
- —High-volume KYC pipelines requiring bulk pricing or SLAs
- —Use cases requiring detailed documentation of input/output schemas before integration
- —Regulated environments that need a named, audited KYC provider with certifications
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/kyc/verifications/98 \
-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 body fields, response schema, or what 'verifications/98' actually verifies. Docs pages are empty. No OpenAPI spec. Effectively a stub listing.
Warnings
- —No documentation available — docs, pricing, and API pages all show only 'Connect wallet' with no content.
- —Request body schema and response format are completely unknown; example_request_json and example_response_json cannot be provided.
- —The endpoint path includes a numeric ID (/98) whose meaning is undocumented — it may be a specific verification type or a placeholder.
- —KYC/identity verification is a regulated category; no information about the provider's compliance certifications or data handling practices is available.
- —The provider's identity and legal entity are not disclosed on the site.
Citations
- —The endpoint returns a valid x402 challenge with maxAmountRequired of 20000 base units in USDC on Basehttps://lowpaymentfee.com/api/v1/kyc/verifications/98
- —USDC contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/kyc/verifications/98
- —All APIs on the site are priced at $0.02 per request with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com
- —The site lists KYC/verification, analytics, AI, finance, and utility API categorieshttps://lowpaymentfee.com