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

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/59` 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 parent site lowpaymentfee.com hosts a broad 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 verification endpoint's input schema, required POST body fields, and response format are not documented in any crawled page. The docs, pricing, and API pages all resolve to a minimal "Connect wallet" prompt with no further detail. Because of this, the exact capabilities and data returned by the KYC verification call remain unclear.

Payment settles on Base using USDC (contract 0x8335…2913) to address 0x1A2B…85F3, with a maximum timeout of 300 seconds. The endpoint is live and returning a valid x402 challenge (HTTP 402).

Capabilities

kyc-verificationx402-paymentusdc-settlementbase-networkper-call-pricingno-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 pay-per-call KYC without subscription commitments
  • —AI agents that can settle payments via x402 on Base
  • —Web3 applications requiring on-demand identity verification

Not for

  • —Bulk KYC processing where per-call 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/59 \
  -H "Content-Type: application/json" \
  -H "X-PAYMENT: <x402_payment_token>" \
  -d '{}'

Endpoint

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

Quality

0.30/ 1.00

The endpoint is live and returns a valid x402 challenge, but there is zero documentation on the request body schema, response format, or what the KYC verification actually checks. Docs pages are empty stubs. The endpoint path includes a hardcoded ID (59) with no explanation. Effectively a stub listing.

Warnings

  • —No documentation available — docs, pricing, and API pages all show only 'Connect wallet' with no content.
  • —Request body schema and response format are completely unknown; the POST body fields required for KYC verification are undocumented.
  • —The endpoint path contains a hardcoded resource ID (/59) whose meaning is unclear.
  • —No OpenAPI spec, no examples, and no AI plugin manifest found.
  • —KYC/identity verification is a regulated category — verify the provider's compliance posture before relying on this in production.

Citations

Provenance

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

Agent access

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