x402basequality 0.35

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

Price
0.02 USDC / call
Protocol
x402
Verified
no

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/78` 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, 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, so callers should expect to experiment or contact the provider for details on required POST body fields.

Settlement occurs on Base mainnet to address `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3` using USDC (contract `0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913`). The x402 challenge specifies a maximum timeout of 300 seconds and uses the "exact" payment scheme at version 1.

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 compliance verification into agent-driven workflows
  • Adding pay-per-use identity verification to Web3 applications

Fit

Best for

  • Developers needing on-demand KYC verification without subscription commitments
  • AI agents that need to programmatically trigger identity checks
  • Web3 applications requiring low-friction compliance endpoints

Not for

  • High-volume KYC pipelines needing bulk pricing or SLAs
  • Use cases requiring detailed documentation or guaranteed uptime commitments
  • Scenarios where the specific verification methodology must be audited beforehand

Quick start

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

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.35/ 1.00

The endpoint is live and returns a valid x402 402 challenge, but there is no documentation on request/response schemas, no OpenAPI spec, and the KYC endpoint is not listed on the provider's homepage. The actual functionality behind the endpoint is unverifiable from available material.

Warnings

  • No request or response schema documented — callers must guess at required POST body fields.
  • This endpoint (/api/v1/kyc/verifications/78) is not listed on the provider's public homepage; its functionality is unverified.
  • KYC/identity verification is a regulated category — verify the provider's compliance credentials before relying on this in production.
  • The '/78' suffix suggests a resource-specific ID rather than a general-purpose endpoint; unclear if this is reusable or a one-off resource.
  • Docs, pricing, API, and README pages all returned only 'Connect wallet' with no substantive content.

Citations

Provenance

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

Agent access