x402basequality 0.30

Pay-per-call transaction receipt endpoint on Base via x402, settled in USDC at $0.02/request.

Price
0.02 USDC / call
Protocol
x402
Verified
no

What it does

This x402-enabled endpoint at lowpaymentfee.com provides a "Premium API Access" receipt for transaction ID 91. It is part of a broader platform offering dozens of pay-per-call API endpoints spanning data analytics, AI/ML inference, finance/Web3 data, and infrastructure utilities — all priced at $0.02 per request and settled in USDC on the Base network.

The specific endpoint `/api/v1/transactions/91/receipt` accepts POST requests and returns JSON. Payment is handled via the x402 protocol: callers attach an `X-PAYMENT` header containing a signed USDC payment of up to 20,000 base units (i.e., $0.02 given USDC's 6 decimals) to the payee address `0x1A2B...85F3` on Base. No API keys, rate limits, or upfront commitments are required — access is instant once payment is included.

Documentation on the site is extremely sparse; the docs, API, pricing, and README pages all render only a "Connect wallet" prompt with no substantive content. There is no OpenAPI spec, no request/response schema beyond the x402 challenge's `outputSchema`, and no examples of what the receipt payload actually contains. The platform lists many other endpoints (sentiment analysis, summarization, embeddings, price feeds, gas estimates, geocoding, etc.) at the same $0.02 price point, but none have documented schemas either. Treat this listing as a stub until richer documentation becomes available.

Capabilities

x402-paymentusdc-settlementbase-networktransaction-receiptpay-per-callno-api-keyjson-response

Use cases

  • Retrieving a transaction receipt for transaction 91 via a single paid API call
  • Demonstrating x402 pay-per-call integration on the Base network
  • Programmatic receipt fetching without API key management

Fit

Best for

  • Developers experimenting with x402 protocol payments
  • Agents that need on-demand, keyless API access settled in USDC
  • Projects requiring Base-network micropayment integration examples

Not for

  • Production workloads requiring well-documented request/response schemas
  • Bulk or high-volume receipt retrieval (no batch endpoint documented)
  • Users who need fiat-only payment rails

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/transactions/91/receipt \
  -H "X-PAYMENT: <x402-signed-payment-header>" \
  -H "Content-Type: application/json"

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.30/ 1.00

The endpoint is live (402 challenge captured) and pricing is clear ($0.02 USDC on Base), but there is no OpenAPI spec, no request/response schema, no documentation beyond a wallet-connect prompt, and the specific purpose of this receipt endpoint is unexplained. Effectively a stub.

Warnings

  • No OpenAPI or schema documentation available — request body and response format are unknown.
  • All non-homepage pages (docs, API, pricing, README) render only 'Connect wallet' with no content.
  • The endpoint path includes a hardcoded transaction ID (91); it is unclear whether this is parameterized or fixed.
  • The broader platform lists many endpoints (AI, finance, utils) but none have documented schemas or examples.

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-19 13:53:45Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-18
Last seen2026-04-23

Agent access