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/9` 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 parent site lowpaymentfee.com hosts a broad 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, the specific KYC verification endpoint's input schema, required POST body fields, and response format are not documented in any crawled page. The docs, pricing, and API pages all resolve to a minimal "Connect wallet" prompt with no further detail. Because of this, the exact verification capabilities (document check, identity match, sanctions screening, etc.) and expected request/response payloads remain unknown.
The endpoint is confirmed live: it returns a well-formed x402 version-1 challenge with scheme "exact", settling to address 0x1A2B…85F3 in USDC (contract 0x8335…2913) on Base. The maximum amount required is 20,000 base units, which at 6 decimals equals $0.02 USD per call.
Capabilities
Use cases
- —Verifying customer identity as part of onboarding flows
- —Performing KYC checks without managing API keys or subscriptions
- —Integrating compliance verification into agent-driven workflows
- —Adding pay-per-use identity checks to Web3 applications
Fit
Best for
- —Developers needing low-friction, pay-per-call KYC checks
- —Agent workflows that can settle payments via x402 on Base
- —Projects that want to avoid API key management for compliance endpoints
Not for
- —Users who need detailed documentation or guaranteed SLAs before integrating
- —Bulk KYC processing where per-call pricing may not be cost-effective
- —Environments that cannot settle USDC on the Base network
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/kyc/verifications/9 \
-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 the KYC verification's input fields, expected POST body, response schema, or what kind of verification is performed. Docs pages are empty stubs. This is effectively a stub listing.
Warnings
- —No documentation available for this endpoint — input schema and response format are completely unknown.
- —The nature of the KYC verification (document check, identity match, sanctions screening, etc.) is unspecified.
- —All doc/pricing/API pages on the site resolve to a minimal 'Connect wallet' prompt with no content.
- —KYC/identity verification is a regulated category — verify the provider's compliance posture before relying on this in production.
- —The endpoint path includes a numeric ID (/9) whose meaning is unclear — it may refer to a specific verification type or record.
Citations
- —The endpoint returns a valid x402 version-1 challenge with maxAmountRequired of 20000 base units in USDC on Basehttps://lowpaymentfee.com/api/v1/kyc/verifications/9
- —All APIs on the site are priced at $0.02 per request with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/kyc/verifications/9