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

What it does

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

The specific endpoint `/api/v1/transactions/335/receipt` accepts POST requests and returns `application/json`. Payment is handled via the x402 protocol: callers must include an `X-PAYMENT` header with a valid payment proof. The x402 challenge advertises a max amount of 20,000 base units of USDC (0x8335…2913 on Base), which equals $0.02 given USDC's 6 decimals. The payment is sent to address `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3` with a timeout of 300 seconds.

The platform advertises no API keys, no rate limits, and instant access. However, documentation pages (`/docs`, `/pricing`, `/api`, `/README`) all resolve to a minimal "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 confirmed live (returns 402 challenge), but the lack of documentation makes it difficult to know what data is returned or what input the POST body expects.

Capabilities

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

Use cases

  • —Retrieving a transaction receipt for transaction 335 via a single paid API call
  • —Demonstrating x402 protocol integration for pay-per-call endpoints
  • —Programmatic access to receipt data without API key management

Fit

Best for

  • —Developers experimenting with x402 protocol payments
  • —Agents that can settle USDC payments on Base for per-call access
  • —Use cases requiring keyless, pay-as-you-go API access

Not for

  • —Production workloads requiring documented request/response schemas
  • —Users who need free or subscription-based access rather than per-call crypto payments
  • —Anyone needing bulk or batch transaction receipt retrieval

Quick start

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

Endpoint

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

Quality

0.30/ 1.00

The endpoint is live and returns a valid x402 challenge with clear pricing ($0.02 USDC on Base). However, there is no OpenAPI spec, no documentation of request body or response schema, and all doc pages are empty stubs. The specific purpose of this receipt endpoint is unclear beyond its URL path. Effectively a stub listing.

Warnings

  • —No OpenAPI or schema documentation available — request body and response format are unknown
  • —All documentation pages (/docs, /pricing, /api, /README) return only a 'Connect wallet' prompt with no content
  • —The endpoint is for a specific transaction ID (335); it is unclear whether this is a demo or a general-purpose receipt endpoint
  • —No examples of actual response data are available

Citations

Provenance

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

Agent access

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