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/152/receipt

What it does

This endpoint at lowpaymentfee.com provides a transaction receipt resource (specifically for transaction ID 152) behind an x402 paywall. The provider operates a broader platform offering multiple API categories — data & analytics, AI & machine learning, finance & Web3, and infrastructure utilities — all priced at $0.02 per request and settled in USDC on the Base network via the x402 protocol. No API keys, rate limits, or upfront commitments are required; callers simply attach an X-PAYMENT header with a valid x402 payment proof.

The specific endpoint `/api/v1/transactions/152/receipt` accepts POST requests and returns application/json. The x402 challenge confirms the asset is USDC (contract 0x8335…2913 on Base) with a maxAmountRequired of 20000 base units, which equals $0.02 (USDC uses 6 decimals). The payment is sent to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 with a 300-second timeout.

Documentation on the site is extremely thin — 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 documentation, and no examples of what the receipt payload actually contains. The endpoint is live (returning a proper 402 challenge), but the lack of documentation makes it difficult to know exactly what data the receipt includes or what input parameters the POST body expects.

Capabilities

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

Use cases

  • —Retrieving a transaction receipt for transaction 152 via programmatic x402 payment
  • —Demonstrating x402 protocol integration for pay-per-request APIs
  • —Agents autonomously purchasing transaction data without API key provisioning

Fit

Best for

  • —Developers experimenting with x402 protocol payments on Base
  • —Agents that need to fetch transaction receipts without pre-registration
  • —Low-friction, keyless API access settled in USDC

Not for

  • —Bulk retrieval of many different transaction receipts (only transaction 152 is documented at this endpoint)
  • —Users who need detailed API documentation or response schema guarantees before integrating
  • —Non-crypto workflows that cannot produce x402 payment headers

Quick start

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

Endpoint

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

Quality

0.35/ 1.00

The endpoint is live and returns a valid x402 402 challenge with clear pricing ($0.02 USDC on Base). However, there is no OpenAPI spec, no documentation of request parameters or response schema, and the docs/pricing/README pages are all empty beyond a wallet-connect prompt. The specific purpose of a 'transaction 152 receipt' is unexplained. This is effectively a stub listing.

Warnings

  • —No OpenAPI or schema documentation available — request body and response format are unknown
  • —Docs, API, pricing, and README pages all render only 'Connect wallet' with no substantive content
  • —This endpoint is scoped to a single transaction ID (152); unclear if other transaction IDs are available at similar paths
  • —The broader platform advertises many API categories (AI, analytics, finance, utilities) but none have documented schemas

Citations

Provenance

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

Agent access

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