x402basequality 0.30

Transaction receipt retrieval via x402 micropayment on Base network for $0.02 per request.

Price
0.02 USDC / call
Protocol
x402
Verified
no
Endpoint
https://lowpaymentfee.com/api/v1/transactions/241/receipt

What it does

This endpoint at lowpaymentfee.com provides access to a specific transaction receipt (transaction ID 241) behind an x402 paywall. It is part of a broader platform that offers a variety of pay-per-request APIs spanning data analytics, AI/ML inference, finance/Web3 data, and infrastructure utilities — all priced at $0.02 per call and settled in USDC on the Base network.

The specific endpoint `/api/v1/transactions/241/receipt` accepts POST requests and returns JSON. Payment is handled via the x402 protocol: callers must include an `X-PAYMENT` header with a valid payment proof. The maximum amount required is 20,000 base units of USDC (0x8335…2913 on Base), which equals $0.02 given USDC's 6 decimals. There are no API keys, no rate limits, and no subscription commitments — each request is independently paid for.

Documentation on the site 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 detailed explanation of what the receipt payload contains or what inputs the POST body expects. The platform appears to be a demonstration or early-stage deployment of x402-gated APIs rather than a mature production service.

Capabilities

x402-paymentusdc-basepay-per-requesttransaction-receiptjson-responseno-api-key

Use cases

  • —Retrieving a transaction receipt for transaction 241 via programmatic micropayment
  • —Demonstrating x402 protocol integration for pay-per-request APIs
  • —Building agent workflows that pay for data access in USDC on Base

Fit

Best for

  • —Developers experimenting with x402 protocol payments
  • —Agents that need to pay per call without API key management
  • —Accessing transaction receipts without subscription overhead

Not for

  • —Production workloads requiring detailed API documentation and SLAs
  • —Bulk retrieval of many different transaction receipts (only transaction 241 is exposed at this endpoint)
  • —Users who need fiat-only payment rails

Quick start

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

Endpoint

URLhttps://lowpaymentfee.com/api/v1/transactions/241/receipt
Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.30/ 1.00

The endpoint is live and returns a valid x402 402 challenge, confirming it exists and accepts payments. However, there is no OpenAPI schema, no request/response examples, and the documentation pages are empty stubs. The endpoint is scoped to a single transaction ID (241) with no explanation of what the receipt contains or what POST body is expected. This is effectively a stub listing.

Warnings

  • —Documentation pages (/docs, /api, /pricing, /README) all return only 'Connect wallet' with no usable content.
  • —No OpenAPI or schema available — request body and response format are unknown.
  • —Endpoint is hardcoded to transaction ID 241; unclear if other transaction IDs are available or what this receipt represents.
  • —Platform appears to be a demo or early-stage deployment; production readiness is uncertain.

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-19 12:46:39Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-18
Last seen2026-04-24

Agent access

JSONhttps://clawmart.sh/api/listings/dDzVY7
Transaction receipt retrieval via x402 micropayment on Base network for $0.02 per request. — Clawmart · Clawmart