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 via the x402 payment protocol. The specific resource `/api/v1/kyc/verifications/19` accepts POST requests and charges up to $0.02 per call in USDC on the Base network. Payment is handled inline via the x402 header — no API keys, accounts, or rate limits are required.
The provider's site hosts a broader catalog of pay-per-call APIs spanning data analytics, AI/ML inference, finance/Web3 data, and infrastructure utilities, all priced at $0.02 per request. However, this particular endpoint falls under a KYC/verification category that is not explicitly listed on the provider's landing page, so its exact input schema and response format are unknown. The x402 challenge confirms the endpoint is live and accepts POST requests with a JSON MIME type, settling payments to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 using USDC (contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) on Base.
Documentation is extremely sparse — the docs, pricing, and API pages all render only a "Connect wallet" prompt with no further content. The request body schema and response schema are not documented anywhere in the crawled material, making it difficult to use this endpoint without trial-and-error or additional out-of-band information.
Capabilities
Use cases
- —Verifying customer identity as part of an onboarding flow
- —Performing KYC checks before granting access to regulated services
- —Automating compliance verification in a Web3 application
Fit
Best for
- —Developers needing pay-per-call KYC without subscription commitments
- —Web3 applications that can settle micropayments in USDC on Base
- —Agents that need programmatic identity verification via x402
Not for
- —Teams requiring detailed API documentation before integration
- —High-volume KYC pipelines where per-call pricing may not be cost-effective
- —Use cases requiring non-crypto payment rails
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/kyc/verifications/19 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402_payment_token>" \
-d '{}'Endpoint
Quality
The x402 challenge is live and confirms pricing and network details, but there is zero documentation on request/response schemas, no OpenAPI spec, and the KYC endpoint is not even listed on the provider's own landing page. Effectively a stub listing.
Warnings
- —No request or response schema documented — input format is unknown
- —KYC verification endpoint not listed on the provider's public API catalog
- —All documentation pages (docs, pricing, API, README) render only 'Connect wallet' with no content
- —KYC/identity verification may be subject to regulatory requirements — verify compliance before use
- —The path segment '/19' suggests a resource ID; it is unclear whether this is a fixed endpoint or a parameterized path
Citations
- —The endpoint returns a 402 challenge requesting USDC payment on Base networkhttps://lowpaymentfee.com/api/v1/kyc/verifications/19
- —USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/kyc/verifications/19
- —maxAmountRequired is 20000 base units (= $0.02 USDC with 6 decimals)https://lowpaymentfee.com/api/v1/kyc/verifications/19
- —Provider advertises $0.02/request pricing with no API keys, no rate limitshttps://lowpaymentfee.com
- —Documentation pages render only 'Connect wallet' with no substantive contenthttps://lowpaymentfee.com/docs