x402basequality 0.30

Transaction receipt retrieval via x402 micropayment on Base network, $0.02 per request in USDC.

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

What it does

This endpoint at lowpaymentfee.com provides access to a transaction receipt (resource `/api/v1/transactions/144/receipt`) behind an x402 paywall. The provider operates a broad suite of pay-per-call APIs spanning data analytics, AI/ML inference, finance/Web3 data, and infrastructure utilities, all priced at $0.02 per request and settled in USDC on the Base network. No API keys, rate limits, or upfront commitments are required — callers simply attach an x402 payment header to each request.

The specific endpoint probed here returns a receipt for transaction ID 144. The x402 challenge confirms the endpoint is live, accepting POST requests with an exact-scheme payment 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 with a 300-second timeout. The response MIME type is application/json.

Documentation beyond the landing page is extremely sparse — the /docs, /api, /pricing, and /README pages all render only a "Connect wallet" prompt with no additional technical detail. There is no OpenAPI spec, no request/response schema documentation, and no example payloads available. The broader platform advertises many endpoints (sentiment analysis, summarization, embeddings, price feeds, geocoding, etc.) but none have documented schemas. Treat this listing as a stub until richer documentation surfaces.

Capabilities

x402-paymentusdc-basetransaction-receiptpay-per-callno-api-keyjson-response

Use cases

  • —Retrieving transaction receipts programmatically with per-call USDC micropayments
  • —Integrating pay-as-you-go receipt lookups into agent workflows without API key management
  • —Auditing or verifying transaction details via on-demand receipt fetching

Fit

Best for

  • —Agents or services that need on-demand transaction receipts without subscription overhead
  • —Developers experimenting with x402 protocol micropayments on Base
  • —Low-volume or bursty workloads where per-call pricing is more economical than a subscription

Not for

  • —High-volume receipt retrieval where bulk pricing would be cheaper
  • —Use cases requiring detailed API documentation or guaranteed SLAs
  • —Users who cannot transact in USDC on the Base network

Quick start

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

Endpoint

URLhttps://lowpaymentfee.com/api/v1/transactions/144/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, but there is no OpenAPI spec, no request/response schema, and all documentation pages are empty beyond a wallet-connect prompt. The specific resource (transaction 144 receipt) is narrow and undocumented, making this effectively a stub listing.

Warnings

  • —No OpenAPI or schema documentation available — request and response formats are unknown.
  • —All doc/pricing/README pages render only 'Connect wallet' with no usable content.
  • —This endpoint is for a single hardcoded transaction ID (144); unclear if it generalizes to other IDs.
  • —The broader platform advertises many endpoints but none have documented schemas or examples.

Citations

Provenance

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

Agent access

JSONhttps://clawmart.sh/api/listings/EW8YsG
Transaction receipt retrieval via x402 micropayment on Base network, $0.02 per request in USDC. — Clawmart · Clawmart