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/31`. It uses the x402 payment protocol, accepting USDC on the Base network. The x402 challenge advertises a maximum amount of 20,000 base units of USDC (6 decimals), which equals $0.02 per request. Payment is made inline via the X-PAYMENT header with no API keys or rate limits required.
The provider's landing page lists a broad catalog of pay-per-call APIs spanning data analytics, AI/ML inference, finance/Web3, and infrastructure utilities — all priced at $0.02 per request. However, the specific endpoint being listed here (`/api/v1/kyc/verifications/31`) is not explicitly documented on the landing page or in any crawled documentation. The path suggests a KYC verification resource (possibly a specific verification record or template identified by ID 31), but without further documentation or example request/response payloads, the exact input parameters and response format remain unknown.
The endpoint is confirmed live — it returns a proper 402 challenge with x402 version 1. The payment is settled to address `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3` using the USDC contract `0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913` on Base. The timeout for payment is 300 seconds. No OpenAPI schema, detailed docs, or example responses were found in the crawl.
Capabilities
Use cases
- —Verifying customer identity as part of onboarding flows
- —Compliance checks for financial or regulated services
- —Automated KYC lookups triggered by agent workflows
Fit
Best for
- —Developers needing on-demand KYC verification without subscription commitments
- —Agent-based workflows requiring inline crypto-paid identity checks
- —Low-volume or bursty KYC needs at $0.02 per call
Not for
- —High-volume KYC pipelines needing bulk pricing or SLAs
- —Use cases requiring detailed documentation and guaranteed response schemas before integration
- —Users who cannot pay with USDC on Base
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/kyc/verifications/31 \
-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 no documentation, no OpenAPI schema, no example requests or responses, and the specific KYC endpoint is not even listed on the provider's own landing page. The purpose and input/output format must be inferred entirely from the URL path.
Warnings
- —The endpoint /api/v1/kyc/verifications/31 is not listed on the provider's landing page among their documented APIs.
- —No request or response schema is available — input parameters and output format are completely unknown.
- —The docs, pricing, API, and README pages all returned only a 'Connect wallet' prompt with no useful content.
- —The hardcoded ID '31' in the path is unexplained — it may refer to a specific verification record rather than a general-purpose endpoint.
Citations
- —The x402 challenge advertises maxAmountRequired of 20000 base units of USDC on Base, equaling $0.02 per request.https://lowpaymentfee.com/api/v1/kyc/verifications/31
- —The provider lists all APIs at $0.02 per request with no API keys, no rate limits, and instant access on Base network.https://lowpaymentfee.com
- —USDC contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 and payment goes to 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3.https://lowpaymentfee.com/api/v1/kyc/verifications/31