x402basequality 0.35

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

Price
0.02 USDC / call
Protocol
x402
Verified
no
Endpoint
https://lowpaymentfee.com/api/v1/kyc/verifications/3

What it does

This endpoint at lowpaymentfee.com provides a KYC (Know Your Customer) verification service accessible via the x402 payment protocol. The specific route `/api/v1/kyc/verifications/3` accepts POST requests and charges up to $0.02 per call in USDC on the Base network. No API keys or rate limits are required — callers simply attach an x402 payment header to each request.

The broader lowpaymentfee.com platform hosts a variety of pay-per-request APIs spanning data analytics, AI/ML inference (sentiment analysis, summarization, classification, embeddings), finance and crypto market data, and infrastructure utilities. All endpoints share the same $0.02/request pricing model settled in USDC on Base. However, the specific KYC verification endpoint's input schema, required fields, and response format are not documented in any crawled material, so the exact verification capabilities and data returned remain unclear.

The endpoint is live and returns a valid x402 challenge (HTTP 402) with version 1 of the protocol. Payment is made to address `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3` using USDC (`0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913`) on Base, with a maximum timeout of 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 key subscriptions
  • —Integrating identity verification into agent-driven workflows
  • —Adding compliance checks to Web3 or DeFi applications

Fit

Best for

  • —Developers needing low-friction KYC verification without signup
  • —AI agents that can settle payments on Base via x402
  • —Applications requiring pay-as-you-go identity checks

Not for

  • —High-volume KYC pipelines where per-request pricing may add up versus bulk plans
  • —Use cases requiring detailed documentation or SLA guarantees (docs are minimal)
  • —Regulated environments requiring auditable vendor certifications (no compliance info available)

Quick start

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

Endpoint

URLhttps://lowpaymentfee.com/api/v1/kyc/verifications/3
Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.35/ 1.00

The endpoint is live and returns a valid x402 challenge, but there is no documentation on request/response schemas, no OpenAPI spec, and the crawled docs pages are empty stubs. The KYC verification functionality cannot be verified beyond the URL path name.

Warnings

  • —No request or response schema documented — input fields for KYC verification are unknown
  • —Documentation pages (/docs, /api, /pricing, /README) returned only 'Connect wallet' with no actual content
  • —The specific nature of 'verifications/3' (what the '3' refers to) is unexplained
  • —No compliance certifications or data handling policies are documented for a KYC/identity service

Citations

Provenance

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

Agent access

JSONhttps://clawmart.sh/api/listings/EsF2Pv
KYC verification endpoint on Base, pay-per-call via x402 with USDC. — Clawmart · Clawmart