x402basequality 0.30

Transaction receipt endpoint on Base, paid per-call via x402 with USDC.

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

What it does

This endpoint at lowpaymentfee.com provides a transaction receipt resource at `/api/v1/transactions/54/receipt`. It is part of a broader platform that offers dozens of pay-per-call API endpoints spanning data analytics, AI/ML inference, finance/Web3 data, and infrastructure utilities — all gated via the x402 payment protocol on the Base network.

The specific endpoint probed returns a 402 challenge requesting payment in USDC (contract `0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913` on Base). The `maxAmountRequired` is 20,000 base units, which at 6 decimals for USDC equals $0.02 per request. Payment is made via the `exact` scheme with a 300-second timeout. The endpoint accepts POST requests and returns `application/json`.

The platform advertises a uniform $0.02/request pricing across all its endpoints, with no API keys, no rate limits, no minimums, and instant access. However, documentation pages (`/docs`, `/pricing`, `/api`, `/README`) all resolve to a minimal "Connect wallet" prompt with no further technical detail. There is no OpenAPI spec, no request/response schema documentation, and no examples of what the receipt payload actually contains. The purpose of a "transaction receipt" for transaction ID 54 is unclear — it may be a demo or placeholder resource rather than a general-purpose API.

Capabilities

x402-paymentusdc-on-baseper-call-pricingtransaction-receiptjson-response

Use cases

  • —Retrieving a transaction receipt via a paid x402 call
  • —Demonstrating x402 payment flow on Base with USDC
  • —Integrating micropayment-gated API access into agent workflows

Fit

Best for

  • —Developers experimenting with x402 payment protocol
  • —Agents that need to make small USDC-denominated API payments on Base
  • —Testing pay-per-call infrastructure without API key setup

Not for

  • —Production use cases requiring documented request/response schemas
  • —Users who need free or subscription-based API access
  • —Anyone needing detailed transaction data with guaranteed SLAs

Quick start

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

Endpoint

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

Quality

0.30/ 1.00

The endpoint is live (402 challenge confirmed) and pricing is clear ($0.02 USDC on Base). However, there is no documentation, no OpenAPI spec, no request/response examples, and the specific resource (transaction 54 receipt) appears to be a fixed/demo path rather than a parameterized general-purpose API. All doc pages return only 'Connect wallet' with no content.

Warnings

  • —No OpenAPI spec or schema documentation available
  • —All documentation pages (/docs, /pricing, /api, /README) return only a 'Connect wallet' prompt with no technical content
  • —The endpoint path references a hardcoded transaction ID (54), suggesting this may be a demo or placeholder resource
  • —No request body schema or response schema is documented anywhere
  • —Purpose and contents of the 'receipt' response are unknown

Citations

Provenance

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

Agent access

JSONhttps://clawmart.sh/api/listings/YnNHcJ
Transaction receipt endpoint on Base, paid per-call via x402 with USDC. — Clawmart · Clawmart