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 path `/api/v1/kyc/verifications/80` accepts POST requests and charges up to $0.02 per call in USDC on the Base network. Payment is handled inline via the X-PAYMENT header — no API keys, accounts, or rate limits are required.
The broader lowpaymentfee.com platform advertises a 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 verifications endpoint is not listed on the site's public catalog, and no documentation, request schema, or response schema is available for it. The crawled docs, pricing, and API pages all returned only a "Connect wallet" stub with no further content.
Because no input/output schema, example payloads, or detailed documentation were found for this endpoint, its exact functionality — what fields it expects, what verification it performs, and what it returns — remains unknown. Agents should treat this as a stub listing until the provider publishes proper documentation.
Capabilities
Use cases
- —Verifying user identity as part of an onboarding flow
- —Performing KYC checks before enabling financial transactions
- —Automated compliance screening in Web3 applications
Fit
Best for
- —Agents needing on-demand KYC verification without API key management
- —Web3 applications requiring pay-per-call identity checks on Base
Not for
- —Use cases requiring documented request/response schemas before integration
- —High-volume KYC pipelines needing SLA guarantees or support contracts
- —Regulated environments that require auditable vendor documentation
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/kyc/verifications/80 \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402_payment_token>" \
-d '{}'Endpoint
Quality
The endpoint is live (returns a valid 402 x402 challenge), but there is no documentation, no input/output schema, no examples, and the KYC endpoint is not even listed on the provider's own catalog page. Effectively a stub.
Warnings
- —No request or response schema available — input fields for KYC verification are unknown.
- —The /api/v1/kyc/verifications/80 path is not listed on the provider's public API catalog.
- —All documentation pages (docs, pricing, API, README) returned only a 'Connect wallet' stub with no content.
- —KYC/identity verification is a regulated category — verify the provider's compliance posture independently.
- —The '80' in the path is unexplained; it may be a specific verification type or record ID.
Citations
- —The endpoint returns a 402 x402 challenge with maxAmountRequired of 20000 base units of USDC on Basehttps://lowpaymentfee.com/api/v1/kyc/verifications/80
- —USDC asset address 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Base networkhttps://lowpaymentfee.com/api/v1/kyc/verifications/80
- —The site advertises $0.02 per request, no API keys, no rate limits, instant access on Base networkhttps://lowpaymentfee.com
- —The provider lists APIs across data/analytics, AI/ML, finance/Web3, and infrastructure categories but does not list a KYC endpointhttps://lowpaymentfee.com