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/91`. 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 endpoint.
The broader lowpaymentfee.com platform advertises a range of pay-per-call APIs spanning data analytics, AI/ML inference (sentiment analysis, summarization, classification, embeddings), finance/Web3 data (price feeds, exchange rates, token quotes, gas estimates), 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.
Documentation is extremely sparse. The crawled /docs, /api, /pricing, and /README pages all returned only a "Connect wallet" prompt with no substantive content. There is no OpenAPI schema, no request/response examples, and no description of what input the KYC verification endpoint expects or what it returns. The specific meaning of the path segment `91` (possibly a verification type or resource ID) is not documented. Callers should treat this as an experimental or early-stage endpoint and test carefully before relying on it in production.
Capabilities
Use cases
- —Programmatic KYC verification checks for onboarding flows
- —Agent-driven identity verification without managing API keys
- —Pay-per-use compliance checks settled in USDC on Base
Fit
Best for
- —Developers needing on-demand KYC checks without subscription commitments
- —AI agents that can settle micropayments via x402 on Base
- —Projects requiring keyless, pay-as-you-go identity verification
Not for
- —Production compliance workflows requiring documented SLAs and audit trails
- —Users who need detailed documentation or OpenAPI specs before integration
- —High-volume KYC pipelines where per-call pricing may not be cost-effective
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/kyc/verifications/91 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402_payment_proof>" \
-d '{}'Endpoint
Quality
The endpoint is live (returns a valid 402 x402 challenge) and pricing is clear ($0.02/request in USDC on Base). However, there is no documentation, no OpenAPI schema, no request/response examples, and the specific function of this KYC verification endpoint is undocumented. The /docs and other pages are empty beyond a wallet-connect prompt. This is effectively a stub listing.
Warnings
- —No documentation available — /docs, /api, /pricing, and /README pages all return only 'Connect wallet' with no content.
- —No OpenAPI or request/response schema provided; input format and output structure are unknown.
- —The meaning of path segment '91' in /api/v1/kyc/verifications/91 is undocumented.
- —KYC/identity verification is a regulated category — verify the provider's compliance posture before use in production.
- —No information about data handling, privacy policy, or regulatory compliance is available.
Citations
- —The endpoint returns a 402 x402 challenge with USDC on Base network, maxAmountRequired of 20000 base unitshttps://lowpaymentfee.com/api/v1/kyc/verifications/91
- —All endpoints are priced at $0.02/request with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —The USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/kyc/verifications/91