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
Endpoint
https://lowpaymentfee.com/api/v1/transactions/203/receipt

What it does

This endpoint at lowpaymentfee.com provides a transaction receipt resource via the x402 payment protocol. It is part of a broader platform that offers multiple pay-per-request API categories including data & analytics, AI & machine learning, finance & Web3, and infrastructure utilities — all priced at $0.02 per call and settled in USDC on the Base network.

The specific endpoint `/api/v1/transactions/203/receipt` returns a JSON response (MIME type `application/json`) when a valid x402 payment header is supplied. The x402 challenge advertises a `maxAmountRequired` of 20,000 base units of USDC (asset `0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913`), which equals $0.02 given USDC's 6 decimals. The payment scheme is "exact" on the Base L2 network, with a 300-second timeout. No API keys or rate limits are required — access is gated purely by micropayment.

Documentation on the site is extremely thin: the docs, API, pricing, and README pages all render only a "Connect wallet" prompt with no further content. There is no OpenAPI spec, no request/response schema beyond the x402 challenge's `outputSchema` stub, and no explanation of what data the receipt actually contains. The endpoint is confirmed live (returns HTTP 402 with a well-formed x402 challenge), but the lack of documentation makes it difficult to know what fields the receipt includes or what input parameters (if any) the POST body expects.

Capabilities

x402-paymentusdc-micropaymentbase-networktransaction-receiptpay-per-requestno-api-keyjson-response

Use cases

  • —Retrieving a transaction receipt for transaction ID 203 via micropayment
  • —Programmatic access to receipt data without API key registration
  • —Agent-driven workflows that need on-demand transaction documentation

Fit

Best for

  • —Developers experimenting with x402 payment-gated APIs
  • —Agents that can settle USDC micropayments on Base
  • —Use cases requiring keyless, pay-per-call access to transaction receipts

Not for

  • —Production systems needing well-documented request/response schemas
  • —Bulk retrieval of many transaction receipts (no batch endpoint documented)
  • —Users who cannot transact in USDC on the Base network

Quick start

# Send a POST with an x402 payment header to access the receipt
curl -X POST https://lowpaymentfee.com/api/v1/transactions/203/receipt \
  -H "X-PAYMENT: <x402_payment_token>" \
  -H "Content-Type: application/json"

Endpoint

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

Quality

0.35/ 1.00

The endpoint is confirmed live with a valid x402 challenge and clear pricing ($0.02 USDC on Base). However, there is no OpenAPI spec, no documented request/response schema, no examples, and the docs pages are empty stubs. The purpose of the specific receipt resource is unclear beyond its URL path. This is effectively a stub listing.

Warnings

  • —No OpenAPI or schema documentation available — request body and response fields are unknown
  • —All documentation pages (docs, API, pricing, README) render only 'Connect wallet' with no content
  • —The specific resource '/api/v1/transactions/203/receipt' appears to be a single hardcoded transaction ID; it is unclear whether other transaction IDs are supported
  • —No examples of successful responses are available

Citations

Provenance

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

Agent access

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