x402basequality 0.30

Pay-per-call customer data API on Base via x402 — $0.02/request in USDC.

Price
0.02 USDC / call
Protocol
x402
Verified
no

What it does

This endpoint at lowpaymentfee.com provides access to a "Premium API Access" resource at the path `/api/v1/customers/52`. It is part of a broader platform offering dozens of pay-per-request APIs spanning data & analytics, AI & machine learning, finance & Web3, and infrastructure utilities — all priced at $0.02 per request and settled in USDC on the Base network via the x402 protocol.

The specific endpoint `/api/v1/customers/52` accepts POST requests and returns JSON. The x402 challenge confirms it is live, requiring a payment of up to 20,000 base units of USDC (0x8335…2913 on Base, 6 decimals), which equals $0.02 USD per call. Payment is made to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 with a timeout of 300 seconds. No API keys or rate limits are advertised; access is gated purely by micropayment.

Documentation is extremely sparse. The docs, pricing, API, and README pages all render only a "Connect wallet" prompt with no further content. There is no OpenAPI spec, no request/response schema documentation, and no explanation of what the `/api/v1/customers/52` endpoint actually returns or what input it expects. The resource path suggests customer record retrieval or manipulation, but this is speculative. The platform's landing page lists many other endpoints but provides no detailed documentation for any of them.

Capabilities

x402-paymentusdc-basepay-per-requestjson-responsepost-methodno-api-keycustomer-data

Use cases

  • Accessing customer data records via micropayment without API key registration
  • Integrating pay-per-request data access into agent workflows on Base
  • Testing x402 protocol payment flows against a live endpoint

Fit

Best for

  • Developers exploring x402 micropayment-gated APIs
  • Agents needing keyless, pay-per-call data access on Base
  • Prototyping crypto-native API payment integrations

Not for

  • Production use requiring documented request/response schemas
  • Bulk data retrieval where per-call pricing is inefficient
  • Users without USDC on Base network

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/customers/52 \
  -H "Content-Type: application/json" \
  -H "X-PAYMENT: <x402-payment-token>"

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.30/ 1.00

The endpoint is live and returns a valid x402 challenge with clear pricing, but there is zero documentation on what the endpoint accepts or returns. No OpenAPI spec, no examples, no request/response schemas. The docs pages are empty. The specific purpose of /api/v1/customers/52 is unclear.

Warnings

  • No documentation available — docs, pricing, API, and README pages all show only 'Connect wallet' with no content
  • No OpenAPI or schema definition for request or response payloads
  • The purpose and data returned by /api/v1/customers/52 is undocumented and unclear
  • No examples of successful responses available

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-18 23:16:00Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-18
Last seen2026-04-29

Agent access