x402basequality 0.30

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

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

What it does

This endpoint at lowpaymentfee.com provides a KYC (Know Your Customer) verification service accessible at `/api/v1/kyc/verifications/38`. It uses the x402 payment protocol, accepting USDC on the Base network. The endpoint returns a 402 challenge requiring an X-PAYMENT header with payment proof before granting access. The maximum amount required per call is 20,000 base units of USDC (6 decimals), which equals $0.02 per request.

The broader lowpaymentfee.com platform advertises a wide catalog of pay-per-call APIs spanning data analytics, AI/ML inference, finance/Web3, and infrastructure utilities — all priced at $0.02 per request with no API keys, no rate limits, and no commitments. However, this specific listing is for the KYC verifications endpoint. The exact input schema and response format are not documented in the crawled material; the endpoint accepts HTTP POST requests and returns application/json.

Note that while the endpoint is live and responds with a valid x402 challenge, the documentation pages (docs, pricing, API, README) all returned only a "Connect wallet" prompt with no substantive content. The actual request body format and response schema for this KYC verification endpoint are unknown from available sources.

Capabilities

kyc-verificationx402-paymentusdc-base-networkpay-per-callhttp-postjson-response

Use cases

  • —Verifying customer identity as part of onboarding flows
  • —Performing KYC checks for financial or Web3 applications
  • —Automating compliance verification in agent-driven workflows

Fit

Best for

  • —Developers needing a low-cost per-call KYC verification
  • —Agent workflows requiring pay-as-you-go identity checks without API keys
  • —Web3 applications settling micropayments on Base

Not for

  • —Bulk KYC processing where batch pricing is needed (no documented batch endpoint)
  • —Use cases requiring detailed documentation or SLA guarantees (docs are effectively empty)

Quick start

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

Endpoint

URLhttps://lowpaymentfee.com/api/v1/kyc/verifications/38
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 input/output schema, and no examples available. The KYC verification purpose is inferred solely from the URL path; the actual functionality is unverified. Docs pages are all blank beyond a wallet-connect prompt.

Warnings

  • —No documentation available — all doc pages return only 'Connect wallet' with no content.
  • —Request body schema for the KYC verification endpoint is completely unknown.
  • —Response schema is undocumented; the MIME type is application/json but no fields are specified.
  • —The specific endpoint path '/api/v1/kyc/verifications/38' suggests a resource ID (38) which may be specific to a particular verification record rather than a general-purpose endpoint.
  • —KYC/identity verification is a regulated category — verify the provider's compliance posture before use in production.

Citations

Provenance

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

Agent access

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