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/58`. It uses the x402 payment protocol, accepting USDC on the Base network. The endpoint returns a 402 challenge requiring an X-PAYMENT header with an exact-scheme payment of up to 20,000 base units of USDC (i.e., $0.02 per request, since USDC uses 6 decimals). The payment is sent to address `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3`, and the endpoint accepts POST requests with a JSON response.
The broader lowpaymentfee.com platform advertises a wide range of API categories including data analytics, AI/ML inference, finance/Web3, and infrastructure utilities — all priced at $0.02 per request with no API keys, no rate limits, and no commitments. However, this specific endpoint is in the KYC/verifications path, which is not listed on the site's public landing page. No documentation, request schema, or response schema is available for this endpoint beyond what the x402 challenge provides. The `/docs`, `/api`, `/pricing`, and `/README` pages all returned only a "Connect wallet" prompt with no substantive content.
Because the endpoint path includes a numeric ID (`/58`), it may represent a specific verification resource rather than a general-purpose KYC submission endpoint. Without documentation or example payloads, the exact input format and response structure remain unknown.
Capabilities
Use cases
- —Programmatic identity verification for onboarding flows
- —Agent-initiated KYC checks paid per call with USDC
- —Compliance verification without API key management
Fit
Best for
- —Developers needing pay-per-use KYC without subscription commitments
- —AI agents that can settle payments via x402 on Base
- —Applications requiring on-demand identity verification
Not for
- —Bulk KYC processing where per-call pricing is inefficient
- —Users who need detailed API documentation before integration
- —Applications requiring non-crypto payment methods
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/kyc/verifications/58 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-token>" \
-d '{}'Endpoint
Quality
The endpoint is live (402 challenge confirmed) and pricing is clear ($0.02/request in USDC on Base), but there is no documentation, no request/response schema, no examples, and the KYC endpoint is not listed on the site's public API catalog. The docs, pricing, and README pages are all empty. This is effectively a stub listing.
Warnings
- —No request or response schema available — input format is unknown
- —The /kyc/verifications/58 path is not listed on the site's public API catalog, raising questions about its intended use
- —All documentation pages (/docs, /pricing, /README) returned no content beyond a wallet connect prompt
- —The numeric ID in the path (/58) suggests this may be a specific resource rather than a general KYC endpoint
- —KYC/identity verification is a regulated category — verify the provider's compliance credentials before use
Citations
- —The endpoint returns a 402 challenge with maxAmountRequired of 20000 base units of USDC on Base networkhttps://lowpaymentfee.com/api/v1/kyc/verifications/58
- —The site advertises $0.02 per request pricing with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com
- —USDC asset address 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Base networkhttps://lowpaymentfee.com/api/v1/kyc/verifications/58