x402basequality 0.35

x402-gated transaction receipt endpoint on Base, paying $0.02 in USDC per request.

Price
0.02 USDC / call
Protocol
x402
Verified
no

What it does

This endpoint at lowpaymentfee.com provides a transaction receipt resource (transaction ID 81) behind an x402 paywall. It is part of a broader platform that offers a variety of pay-per-call APIs 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/81/receipt` accepts POST requests and returns JSON. Payment is handled via the x402 protocol: callers must include an `X-PAYMENT` header containing a valid payment proof. The x402 challenge advertises a maxAmountRequired of 20,000 base units of USDC (0x8335…2913 on Base), which equals $0.02 given USDC's 6 decimals. The payment is sent to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 with a timeout of 300 seconds.

The platform advertises no API keys, no rate limits, and instant access. Documentation pages (/docs, /pricing, /README) appear to require wallet connection and contain no substantive content in the crawl. There is no OpenAPI spec, no detailed schema for request/response bodies, and no examples of what the receipt payload actually contains. The endpoint is confirmed live (402 challenge captured), but the lack of documentation makes it difficult to know what data is returned.

Capabilities

x402-paymentusdc-settlementbase-networktransaction-receiptpay-per-callno-api-key

Use cases

  • Retrieving a transaction receipt for transaction 81 via programmatic pay-per-call access
  • Demonstrating x402 protocol payment flows on the Base network
  • Integrating low-cost API calls settled in USDC without API key management

Fit

Best for

  • Developers experimenting with x402 payment protocol
  • Agents needing pay-per-call access without signup or API keys
  • Use cases requiring USDC-settled micropayments on Base

Not for

  • Users needing detailed API documentation or response schemas before integrating
  • Bulk or high-throughput receipt retrieval (no documented batch support)
  • Anyone without a Base-compatible USDC wallet

Quick start

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

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.35/ 1.00

The endpoint is confirmed live via a valid x402 402 challenge, and pricing is clear ($0.02 USDC on Base). However, there is no OpenAPI spec, no request/response schema, no documentation content (all doc pages just show 'Connect wallet'), and the specific purpose of this receipt endpoint is unclear. This is effectively a stub listing.

Warnings

  • No OpenAPI or schema documentation available — request and response formats are unknown.
  • All documentation pages (/docs, /pricing, /README) returned only 'Connect wallet' with no substantive content.
  • The endpoint path references a specific transaction ID (81); it is unclear whether this is a generic pattern or a fixed resource.
  • The broader platform lists many API categories (AI, analytics, finance, etc.) but none could be verified beyond the landing page listings.

Citations

Provenance

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

Agent access

x402-gated transaction receipt endpoint on Base, paying $0.02 in USDC per request. — Clawmart · Clawmart