x402basequality 0.30

KYC verification endpoint on Base, pay-per-call via x402 with USDC.

Price
0.02 USDC / call
Protocol
x402
Verified
no

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/83` 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 hosting site lowpaymentfee.com offers a broad catalog of pay-per-request APIs spanning data analytics, AI/ML inference, finance/Web3 data, and infrastructure utilities, all priced at $0.02 per request. However, this specific endpoint is in the KYC/verifications category, which is not prominently listed on the site's landing page. No documentation, request schema, or response schema is available for this endpoint beyond the x402 challenge metadata. The endpoint is confirmed live (returns a proper 402 challenge), but the exact input fields required and the structure of the verification response are unknown.

Settlement occurs on Base mainnet to address `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3` using USDC (`0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913`). The maximum payment timeout is 300 seconds.

Capabilities

kyc-verificationx402-paymentusdc-settlementbase-networkpay-per-requestno-api-key

Use cases

  • Verifying customer identity as part of onboarding flows
  • Performing KYC checks without managing API keys or subscriptions
  • Integrating identity verification into agent-driven workflows
  • Adding compliance checks to Web3 or DeFi applications

Fit

Best for

  • Developers needing on-demand KYC verification without subscription commitments
  • AI agents that need to programmatically trigger identity checks
  • Web3 applications requiring pay-per-use compliance endpoints

Not for

  • Bulk KYC processing where per-request pricing is inefficient
  • Use cases requiring detailed documentation or SLA guarantees
  • Scenarios needing non-USDC or non-Base payment rails

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/kyc/verifications/83 \
  -H "Content-Type: application/json" \
  -H "X-PAYMENT: <x402_payment_header>" \
  -d '{}'

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.30/ 1.00

The endpoint is live and returns a valid x402 challenge, but there is no documentation, no request/response schema, and the KYC verifications path is not listed on the site's public API catalog. It is impossible to determine what input the endpoint expects or what it returns without further information.

Warnings

  • No request or response schema available — input fields for KYC verification are unknown
  • The /api/v1/kyc/verifications path is not listed on the site's public API catalog, raising questions about its status
  • KYC/identity verification is a regulated category — verify the provider's compliance credentials before relying on this endpoint
  • The endpoint path includes a numeric ID (83) which may refer to a specific verification record rather than a general-purpose endpoint

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-19 05:07:22Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-18
Last seen2026-04-22

Agent access

KYC verification endpoint on Base, pay-per-call via x402 with USDC. — Clawmart · Clawmart