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

This endpoint at lowpaymentfee.com provides premium API access to a customer resource (customer ID 91) via the x402 payment protocol. It accepts HTTP POST requests and returns JSON. Payment is settled on the Base network using USDC (contract 0x8335…2913) with a maximum cost of 20,000 base units, which equals $0.02 per request (USDC uses 6 decimals).

The broader lowpaymentfee.com platform advertises a suite of pay-per-call APIs spanning 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 $0.02 per request with no API keys, no rate limits, and no minimum commitments.

The specific endpoint probed (/api/v1/customers/91) is not explicitly listed on the landing page's catalog, so its exact response schema and purpose are unclear beyond the generic "Premium API Access" description. Documentation pages (/docs, /pricing, /README) returned only a wallet-connect prompt with no substantive content, so detailed request/response schemas, field definitions, and usage examples are unavailable.

Capabilities

x402-paymentusdc-settlementbase-networkper-call-pricingjson-responsehttp-postcustomer-data

Use cases

  • Fetching customer data records on demand with per-request USDC micropayments
  • Integrating pay-as-you-go data access into agent workflows without API key management
  • Demonstrating x402 protocol payment flows on the Base network

Fit

Best for

  • Developers experimenting with x402 pay-per-call protocols
  • Agents needing keyless, on-demand API access settled in USDC
  • Low-volume or sporadic data retrieval where subscription pricing is wasteful

Not for

  • High-volume bulk data retrieval where per-call costs add up quickly
  • Use cases requiring detailed API documentation, SLAs, or guaranteed uptime

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/customers/91 \
  -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 live and returns a valid x402 402 challenge, confirming it works. However, the specific /customers/91 resource is not documented on the site, no response schema or example is available, and all documentation pages returned only a wallet-connect stub with no content. The listing is essentially a stub with pricing and protocol details only.

Warnings

  • The /api/v1/customers/91 endpoint is not listed in the site's public API catalog — its purpose and response format are unknown.
  • All documentation pages (/docs, /pricing, /README) returned no substantive content, only a wallet-connect prompt.
  • No OpenAPI spec, request schema, or response schema is available.
  • No information on rate limits, uptime guarantees, or data freshness is provided.

Citations

Provenance

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

Agent access