KYC verification endpoint on Base, pay-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/18`. It is part of a broader platform offering dozens of pay-per-request APIs spanning data analytics, AI/ML inference, finance, crypto, and utility services. All endpoints use the x402 payment protocol, settling in USDC on the Base network.
The specific endpoint probed here costs $0.02 per request (maxAmountRequired of 20,000 base units of USDC, which has 6 decimals = $0.02). Payment is made via the x402 `exact` scheme — callers attach an `X-PAYMENT` header with a signed payment to the payTo address. No API keys or rate limits are advertised; access is gated purely by micropayment. The endpoint accepts POST requests and returns `application/json`.
Documentation is extremely sparse. The landing page lists available API categories and a uniform $0.02/request price, but the docs, pricing, and API pages all render only a "Connect wallet" prompt with no further technical detail. There is no OpenAPI spec, no request/response schema, and no explanation of what the KYC verification endpoint expects as input or returns as output. The endpoint is live (returns a proper 402 challenge), but without documentation it is unclear what request body is required or what verification data is returned.
Capabilities
Use cases
- —Verifying customer identity as part of onboarding flows
- —Compliance checks for financial or crypto applications
- —Automated KYC screening integrated into agent workflows
Fit
Best for
- —Developers needing pay-per-call KYC without subscription commitments
- —Agent-based workflows requiring programmatic identity verification
- —Crypto-native applications already on Base network
Not for
- —Users needing detailed API documentation before integration
- —High-volume KYC pipelines requiring SLAs or guaranteed uptime
- —Regulated entities requiring audit trails and vendor compliance certifications
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/kyc/verifications/18 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <signed-x402-payment-header>" \
-d '{}'Endpoint
Quality
The endpoint is live and returns a valid x402 402 challenge, confirming it exists and accepts payments. However, there is no documentation, no OpenAPI spec, no request/response schema, and no explanation of what the KYC verification endpoint actually does or expects. The listing is effectively a stub.
Warnings
- —No API documentation available — docs, pricing, and API pages all render only a 'Connect wallet' prompt
- —No request or response schema provided; callers cannot determine required input fields
- —The KYC verification category may involve regulated data (PII); no compliance or privacy information is available
- —The endpoint path includes a numeric ID (/18) whose meaning is undocumented
Citations
- —The endpoint returns a 402 challenge with maxAmountRequired of 20000 in USDC on Base networkhttps://lowpaymentfee.com/api/v1/kyc/verifications/18
- —All APIs are priced at $0.02 per request with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com
- —USDC asset address 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/kyc/verifications/18