x402basequality 0.35

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

Price
0.02 USDC / call
Protocol
x402
Verified
no
Endpoint
https://lowpaymentfee.com/api/v1/customers/25

What it does

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

The specific endpoint `/api/v1/customers/25` accepts POST requests and returns JSON. The x402 challenge advertises a maximum cost of 20,000 base units of USDC (0x8335…2913 on Base), which equals $0.02 per request (USDC uses 6 decimals). Payment is made inline via the X-PAYMENT header with no API keys, no rate limits, and no upfront commitments. The payment timeout is 300 seconds.

Documentation on the site is extremely thin — the /docs, /pricing, /api, and /README pages all render only a "Connect wallet" prompt with no additional technical detail. There is no OpenAPI spec, no request/response schema, and no usage examples available from the crawl. The endpoint name suggests it returns customer data for a given ID, but the exact fields and behavior are unverified. The platform lists many other endpoints at $0.02 each across categories like sentiment analysis, text summarization, geocoding, and crypto gas estimates, all using the same x402 payment model on Base.

Capabilities

x402-paymentusdc-basepay-per-requestjson-apicustomer-datano-api-keypost-method

Use cases

  • —Retrieving customer records on a per-request payment basis without API key management
  • —Integrating pay-as-you-go data access into agent workflows via x402
  • —Accessing structured customer data from an x402-enabled endpoint on Base

Fit

Best for

  • —Agents or services that need on-demand customer data without subscription overhead
  • —Developers experimenting with x402 payment protocol integrations
  • —Low-volume or bursty access patterns where per-call pricing is cost-effective

Not for

  • —High-volume bulk data retrieval where per-request fees would accumulate quickly
  • —Use cases requiring detailed API documentation or guaranteed SLAs
  • —Users without a Base-compatible USDC wallet

Quick start

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

Endpoint

URLhttps://lowpaymentfee.com/api/v1/customers/25
Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.35/ 1.00

The endpoint is live and returns a valid x402 402 challenge with clear pricing. However, there is no OpenAPI spec, no request/response schema, no documentation beyond a wallet-connect prompt, and no examples. The purpose of the specific /customers/25 path is unclear — it could be a demo or placeholder. This is effectively a stub listing.

Warnings

  • —No OpenAPI or schema documentation available — request and response formats are unknown
  • —All documentation pages (/docs, /pricing, /api, /README) render only 'Connect wallet' with no content
  • —The endpoint path /api/v1/customers/25 with a hardcoded ID may be a demo/placeholder rather than a production resource
  • —No information on what customer data is returned or what POST body is expected

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-18 22:38:15Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-18
Last seen2026-04-29

Agent access

JSONhttps://clawmart.sh/api/listings/xHtCR5
Pay-per-call customer data API on Base via x402 — $0.02/request in USDC. — Clawmart · Clawmart