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/57` 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 mechanism — 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 capabilities of the KYC verification (e.g., what identity documents or data it accepts, what jurisdictions it covers, what it returns) remain unknown.
The endpoint is live: it returns a well-formed x402 challenge (HTTP 402) with version 1, 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.
Capabilities
Use cases
- —Verifying user identity as part of onboarding flows
- —Compliance checks for financial or Web3 applications
- —Automated KYC screening without managing API keys or subscriptions
Fit
Best for
- —Developers needing pay-per-call KYC without account setup
- —Web3 apps that already settle on Base and want inline USDC payments
- —Agents or bots that need programmatic identity verification
Not for
- —Users who need detailed documentation before integrating (docs are essentially empty)
- —High-volume KYC pipelines requiring bulk pricing or SLAs
- —Regulated entities that need audit trails and vendor compliance certifications
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/kyc/verifications/57 \
-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 request/response schemas, required fields, or what the KYC verification actually does. Docs pages are empty stubs. The listing is effectively a stub.
Warnings
- —No documentation available — docs, pricing, API, and README pages all show only 'Connect wallet' with no content.
- —Request body schema for the KYC verification POST is completely unknown; no OpenAPI spec or examples exist.
- —Response format and fields are undocumented.
- —The nature and scope of the KYC verification (jurisdictions, document types, data sources) is unspecified.
- —This endpoint may involve regulated personal data (PII); integrators should perform their own compliance review.
Citations
- —The endpoint returns a valid x402 challenge with maxAmountRequired of 20000 base units in USDC on Basehttps://lowpaymentfee.com/api/v1/kyc/verifications/57
- —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/57