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

What it does

This endpoint at lowpaymentfee.com provides access to a transaction receipt (transaction ID 310) behind an x402 paywall. It is part of a broader platform that offers a variety of pay-per-request API endpoints spanning data analytics, AI/ML inference, finance/Web3 data, and infrastructure utilities — all priced at $0.02 per call, settled in USDC on the Base network.

The specific endpoint `/api/v1/transactions/310/receipt` accepts POST requests and returns a JSON response upon successful payment. The x402 challenge advertises a maxAmountRequired of 20,000 base units of USDC (0x8335…2913 on Base), which equals $0.02 given USDC's 6 decimals. Payment is sent to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 using the "exact" scheme with a 300-second timeout.

The platform advertises no API keys, no rate limits, and instant access. Documentation pages (/docs, /pricing, /api, /README) all resolve but contain only a "Connect wallet" prompt, so detailed request/response schemas and endpoint-specific documentation are not available. The actual data returned by this receipt endpoint is unclear — it could be a financial transaction receipt, a proof-of-payment artifact, or something else entirely. Without further documentation or example responses, the precise use case remains ambiguous.

Capabilities

x402-paymentusdc-settlementbase-networkpay-per-requesttransaction-receiptjson-responseno-api-key

Use cases

  • —Retrieving a transaction receipt for transaction 310 via a single micropayment
  • —Demonstrating x402 payment protocol integration for agent-to-API commerce
  • —Accessing pay-per-request infrastructure without API key management

Fit

Best for

  • —Developers experimenting with x402 payment protocol
  • —Agents needing on-demand transaction receipts without subscription overhead
  • —Projects requiring USDC-settled micropayment API access on Base

Not for

  • —Users needing detailed API documentation or response schema guarantees
  • —High-volume batch retrieval where per-request pricing is inefficient
  • —Anyone without a Base-compatible USDC wallet

Quick start

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

Endpoint

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

Quality

0.35/ 1.00

The endpoint is live and returns a valid x402 challenge with clear pricing. However, all documentation pages are empty (just 'Connect wallet'), there is no OpenAPI spec, no request/response schema, and the purpose of this specific receipt endpoint is ambiguous. Effectively a stub listing.

Warnings

  • —All documentation pages (/docs, /pricing, /api, /README) return only 'Connect wallet' with no actual content
  • —No request body schema or response schema available — unclear what data this endpoint returns
  • —The endpoint path references a specific transaction ID (310); it is unclear whether this is a generic pattern or a single fixed resource
  • —No OpenAPI or machine-readable API specification found

Citations

Provenance

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

Agent access

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