x402basequality 0.35

x402-gated transaction receipt endpoint on Base, paid per-call in USDC.

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

What it does

This endpoint at lowpaymentfee.com provides a transaction receipt resource (transaction ID 57) behind an x402 paywall. The broader lowpaymentfee.com platform advertises a suite of pay-per-request APIs spanning data analytics, AI/ML inference (sentiment analysis, summarization, classification, embeddings), finance/Web3 data (price feeds, exchange rates, token quotes, gas estimates), and infrastructure utilities (geocoding, validation, conversion, generation). All endpoints are priced at $0.02 per request, settled in USDC on the Base network via the x402 protocol. No API keys or rate limits are advertised; access is instant upon payment.

The specific endpoint `/api/v1/transactions/57/receipt` accepts POST requests and returns `application/json`. The x402 challenge confirms it is live, requesting a maximum of 20,000 base units of USDC (0.02 USD, since USDC uses 6 decimals) paid to address `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3` on Base. The payment scheme is "exact" with a 300-second timeout. No OpenAPI spec, detailed documentation, or example responses were found in the crawl — the docs, pricing, and API pages all returned only a "Connect wallet" prompt with no further content. The actual data returned by this receipt endpoint is unknown beyond its JSON MIME type.

Capabilities

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

Use cases

  • —Retrieving a transaction receipt for transaction 57 via a single micropayment
  • —Demonstrating x402 protocol integration for pay-per-request APIs
  • —Agent-driven programmatic access to paid data without API key management

Fit

Best for

  • —Developers experimenting with x402 protocol payments on Base
  • —Agents that need keyless, pay-per-call API access settled in USDC
  • —Projects requiring on-chain proof-of-payment for API consumption

Not for

  • —Users needing free or subscription-based API access
  • —Applications requiring detailed API documentation or OpenAPI specs before integration
  • —High-volume batch retrieval where per-call pricing is impractical

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/transactions/57/receipt
# Returns 402 with x402 challenge. Attach X-PAYMENT header with valid USDC payment proof on Base to receive the receipt.

Endpoint

URLhttps://lowpaymentfee.com/api/v1/transactions/57/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 ($0.02 USDC on Base). However, there is no OpenAPI spec, no documentation beyond a wallet-connect prompt, no example request/response payloads, and the actual data returned by this specific receipt endpoint is entirely undocumented. The listing is effectively a stub with confirmed liveness.

Warnings

  • —No OpenAPI or schema documentation available — endpoint behavior must be discovered empirically.
  • —Docs, pricing, API, and README pages all render only a 'Connect wallet' prompt with no usable content.
  • —The specific resource (transaction 57 receipt) is opaque — no description of what fields or data the receipt contains.
  • —The broader platform advertises many endpoints but none were individually verified beyond this one.

Citations

Provenance

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

Agent access

JSONhttps://clawmart.sh/api/listings/pLfvcg
x402-gated transaction receipt endpoint on Base, paid per-call in USDC. — Clawmart · Clawmart