x402basequality 0.30

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

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

What it does

This endpoint at lowpaymentfee.com provides a transaction receipt resource via the x402 payment protocol. The specific path `/api/v1/transactions/5/receipt` returns a receipt for transaction ID 5, gated behind a per-call USDC micropayment on the Base network. The x402 challenge confirms the endpoint is live, accepting POST requests and settling payments in USDC (contract 0x8335…) to the payee address.

The broader lowpaymentfee.com platform advertises a suite of pay-per-request APIs spanning data analytics, AI/ML inference (sentiment analysis, summarization, classification, embeddings), finance/crypto market data, and infrastructure utilities — all priced at $0.02 per request with no API keys, no rate limits, and no commitments. However, the specific endpoint being listed here is the transactions receipt resource, and the x402 challenge shows a maxAmountRequired of 20000 base units of USDC (6 decimals), which equals $0.02.

Documentation 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 schema, no request/response examples, and no detailed documentation for what the receipt payload contains or what parameters the POST body accepts. The endpoint appears functional based on the 402 challenge, but the lack of documentation makes integration speculative.

Capabilities

x402-paymentusdc-micropaymentbase-networktransaction-receiptpay-per-requestno-api-key

Use cases

  • —Retrieving a receipt for a specific transaction on the platform
  • —Programmatic proof-of-payment retrieval for accounting or auditing
  • —Agent-driven workflows that need to verify or archive transaction records

Fit

Best for

  • —Developers experimenting with x402 payment-gated APIs
  • —Agents that need per-call payment without API key management
  • —Retrieving transaction receipts with minimal setup

Not for

  • —Production use requiring well-documented request/response schemas
  • —Bulk or high-throughput receipt retrieval (no documented batch support)
  • —Users who need fiat-only payment rails

Quick start

# The endpoint requires an X-PAYMENT header with a valid x402 payment proof.
# Using curl as a conceptual example (actual payment header must be constructed
# via an x402-compatible client/wallet):

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

Endpoint

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

Quality

0.30/ 1.00

The x402 challenge is live and confirms pricing and network details, but there is zero documentation for the request body, response schema, or what the receipt actually contains. Docs pages are empty beyond a wallet-connect prompt. This is effectively a stub listing.

Warnings

  • —No OpenAPI schema or request/response documentation available
  • —All documentation pages (docs, API, pricing, README) render only 'Connect wallet' with no content
  • —The specific endpoint path includes a hardcoded transaction ID (5); it is unclear how to query other transactions
  • —No examples of the receipt payload structure exist in the crawled material

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-19 13:32:48Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-18
Last seen2026-04-24

Agent access

JSONhttps://clawmart.sh/api/listings/qw3R5G
x402-gated transaction receipt endpoint on Base, paying $0.02 in USDC per request. — Clawmart · Clawmart