x402basequality 0.35

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

Price
0.02 USDC / call
Protocol
x402
Verified
no

What it does

lowpaymentfee.com hosts a collection of pay-per-request APIs accessible via the x402 protocol on the Base network, settling payments in USDC. The specific endpoint `/api/v1/customers/80` is described as "Premium API Access" and returns JSON data when a valid x402 payment header is provided. The x402 challenge advertises a maxAmountRequired of 20,000 base units of USDC (0x8335…), which equals $0.02 per request (USDC uses 6 decimals). No API keys or rate limits are required; access is granted purely through per-call micropayments.

The broader lowpaymentfee.com platform advertises endpoints across several categories: Data & Analytics (metrics, reports, data export, insights), AI & Machine Learning (sentiment analysis, text summarization, classification, embeddings), Finance & Web3 (price feeds, exchange rates, token quotes, gas estimates), and Infrastructure utilities (geocoding, validation, conversion, generation). All endpoints are listed at the same $0.02/request price point. However, the specific endpoint being listed here (`/api/v1/customers/80`) does not clearly map to any of these advertised categories — it appears to be a customer record lookup, though no documentation explains what data it returns.

Documentation is extremely sparse. The /docs, /api, /pricing, and /README pages all render only a "Connect wallet" prompt with no further content. There is no OpenAPI schema, no request/response examples, and no description of the data model returned by this endpoint. The endpoint is confirmed live (402 challenge captured), but the lack of documentation makes it difficult to know what payload to send or what response to expect.

Capabilities

x402-paymentusdc-settlementbase-networkper-call-micropaymentjson-responsecustomer-data-lookup

Use cases

  • Retrieving customer data records via micropayment without API key registration
  • Integrating pay-per-call data access into autonomous agent workflows
  • Demonstrating x402 protocol payment flows on Base

Fit

Best for

  • Agents or services that need keyless, on-demand data access via crypto micropayments
  • Developers experimenting with x402 protocol integrations
  • Use cases where per-request billing is preferred over subscription models

Not for

  • Users who need detailed API documentation or guaranteed SLAs before integrating
  • High-volume consumers who would benefit from bulk pricing or subscriptions
  • Anyone without a Base-network USDC wallet

Quick start

# The endpoint requires an X-PAYMENT header with a valid x402 payment proof.
# Using curl (you need an x402-compatible client to generate the header):
curl -X POST https://lowpaymentfee.com/api/v1/customers/80 \
  -H "Content-Type: application/json" \
  -H "X-PAYMENT: <x402_payment_token>"

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.35/ 1.00

The endpoint is confirmed live via a valid 402 challenge, and pricing is clear ($0.02 USDC on Base). However, there is no OpenAPI schema, no request/response examples, no documentation beyond a wallet-connect prompt, and the purpose of the /api/v1/customers/80 endpoint is unclear. This is effectively a stub listing.

Warnings

  • No API documentation available — /docs, /api, /pricing, and /README pages all show only 'Connect wallet' with no content.
  • No OpenAPI or JSON schema provided; request and response formats are unknown.
  • The endpoint path '/api/v1/customers/80' does not match any of the advertised API categories on the landing page, making its purpose unclear.
  • No request or response examples available to verify functionality beyond the 402 challenge.

Citations

Provenance

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

Agent access