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

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/81` 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 parent site lowpaymentfee.com hosts 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. This particular endpoint falls under a KYC/verification category that is not prominently listed on the homepage but is live and returning a valid 402 challenge. The endpoint's exact input schema and response format are not documented in the crawled material; callers should expect to POST a JSON body and receive a JSON response, but the specific fields required for the verification request are unknown.

Settlement occurs on Base mainnet to a specified wallet address, using the canonical USDC contract (0x8335…). The x402 challenge specifies a maximum timeout of 300 seconds and uses the "exact" payment scheme with x402 version 1.

Capabilities

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

Use cases

  • —Verifying customer identity as part of onboarding flows
  • —Automated KYC checks in Web3 or DeFi applications
  • —Agent-driven compliance verification without pre-registered API keys
  • —On-demand identity verification with per-call micropayments

Fit

Best for

  • —Developers needing keyless, pay-per-use KYC verification
  • —Web3 applications requiring on-chain payment settlement for compliance services
  • —AI agents that need to perform identity checks autonomously

Not for

  • —Bulk KYC processing where per-call pricing is inefficient
  • —Use cases requiring detailed documentation or SLA guarantees
  • —Regulated environments that need audit trails beyond what is documented here

Quick start

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

Endpoint

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

Quality

0.30/ 1.00

The endpoint is live and returns a valid x402 402 challenge, but there is no documentation of the request body schema, response format, or what 'verifications/81' specifically refers to. The docs, pricing, and API pages all returned only a 'Connect wallet' stub with no useful content. The KYC category is not listed on the homepage. This is effectively a stub listing.

Warnings

  • —No input schema or request body documentation available — callers must guess at required fields
  • —KYC/verification endpoints are not listed on the provider's homepage; unclear if this is a production service
  • —KYC services may be subject to regulatory requirements (e.g., data protection, PII handling) — no privacy policy or compliance documentation was found
  • —The '/81' path segment suggests a specific verification record rather than a general-purpose endpoint; purpose is ambiguous
  • —Documentation pages (/docs, /pricing, /api, /README) returned no meaningful content beyond 'Connect wallet'

Citations

Provenance

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

Agent access

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