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

What it does

This endpoint at lowpaymentfee.com provides access to a transaction receipt (resource ID 285) behind an x402 paywall. The broader lowpaymentfee.com platform advertises a suite of APIs spanning data & analytics, AI/ML inference (sentiment analysis, summarization, classification, embeddings), finance & Web3 (price feeds, exchange rates, token quotes, gas estimates), and infrastructure utilities (geocoding, validation, conversion, generation) — all priced at $0.02 per request with no API keys, no rate limits, and no commitments.

The specific probed endpoint (`/api/v1/transactions/285/receipt`) is live and returns a standard x402 challenge on Base network. It accepts payment in USDC (contract 0x8335…2913) with a maxAmountRequired of 20000 base units, which equals $0.02 (USDC uses 6 decimals). Payment is settled on-chain via the x402 "exact" scheme to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3, with a 300-second timeout. The endpoint expects HTTP POST and returns application/json.

Documentation beyond the landing page 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 documentation, and no examples of what the receipt payload actually contains. The platform's claim of 16+ API endpoints at uniform $0.02 pricing is visible on the homepage but none of the individual endpoints are documented in detail.

Capabilities

x402-paymentusdc-settlementbase-networktransaction-receiptper-call-pricingno-api-keyjson-response

Use cases

  • —Retrieving a transaction receipt by paying $0.02 in USDC per call
  • —Demonstrating x402 protocol payment flows on Base network
  • —Agent-driven micropayment API consumption without API key management

Fit

Best for

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

Not for

  • —Production workloads requiring documented request/response schemas
  • —Users who need fiat-only payment options
  • —High-volume batch retrieval where per-call crypto settlement adds overhead

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/transactions/285/receipt
# Returns 402 with x402 challenge; attach X-PAYMENT header with signed USDC payment to access the receipt.

Endpoint

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

Quality

0.30/ 1.00

The endpoint is live and returns a valid x402 challenge, but there is zero documentation on what the receipt payload contains, no OpenAPI spec, no request/response examples, and all doc pages render only 'Connect wallet'. The listing is effectively a stub with only the payment challenge and homepage description to work from.

Warnings

  • —No OpenAPI or schema documentation available — request and response formats are unknown
  • —All documentation pages (/docs, /api, /pricing, /README) render only 'Connect wallet' with no content
  • —The specific endpoint path (/api/v1/transactions/285/receipt) is not listed among the homepage's advertised APIs — its purpose and output are unclear
  • —No examples of successful responses exist in crawled material

Citations

Provenance

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

Agent access

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