x402basequality 0.30

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/70

What it does

This endpoint at lowpaymentfee.com provides a KYC (Know Your Customer) verification service accessible at `/api/v1/kyc/verifications/70`. It uses the x402 payment protocol, accepting USDC on the Base network. Each call costs $0.02 (20,000 base units of USDC with 6 decimals). The endpoint accepts POST requests and returns JSON responses.

The broader lowpaymentfee.com platform offers a suite of pay-per-request APIs spanning data & analytics, AI & machine learning (sentiment analysis, text summarization, classification, embeddings), finance & Web3 (price feeds, exchange rates, token quotes, gas estimates), and infrastructure utilities (geocoding, validation, conversion, generation). All endpoints are priced at $0.02 per request with no API keys, no rate limits, and no minimum commitments — payment is handled entirely via the x402 protocol using USDC on Base.

The specific KYC verification endpoint's input/output schema is not documented in the crawled material. The endpoint is live and returns a valid x402 402 challenge. However, documentation pages (docs, pricing, API reference) all returned only a "Connect wallet" prompt with no substantive content, so the exact request format, required fields, and response structure for KYC verifications remain unknown.

Capabilities

kyc-verificationx402-paymentusdc-basepay-per-requestidentity-verification

Use cases

  • —Verifying customer identity as part of onboarding flows
  • —Performing KYC checks for financial or Web3 applications
  • —Automating compliance verification without managing API keys

Fit

Best for

  • —Developers needing simple pay-per-call KYC verification
  • —Web3 projects requiring on-chain payment for compliance services
  • —Applications that want keyless, no-commitment identity checks

Not for

  • —Bulk KYC processing where per-call pricing is inefficient
  • —Use cases requiring detailed documentation or SLA guarantees
  • —Regulated environments requiring audit trails and vendor certification

Quick start

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

Endpoint

URLhttps://lowpaymentfee.com/api/v1/kyc/verifications/70
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 for the KYC verification endpoint — no input schema, no example requests/responses, and all doc pages are empty. The endpoint path includes a hardcoded ID (70) with no explanation. This is effectively a stub listing.

Warnings

  • —No documentation available — all doc/pricing/API pages return only 'Connect wallet' with no content
  • —Request and response schemas for the KYC verification endpoint are completely unknown
  • —The endpoint path includes a specific ID (/70) whose meaning is unclear — it may be a specific verification type or a placeholder
  • —The KYC verification endpoint is not listed among the provider's advertised APIs on the homepage, raising questions about its status

Citations

Provenance

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

Agent access

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