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

What it does

This endpoint at lowpaymentfee.com provides access to a transaction receipt (transaction ID 87) 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, no rate limits, no subscriptions.

The specific endpoint being listed (`/api/v1/transactions/87/receipt`) accepts POST requests and returns JSON. The x402 challenge confirms it is live, requesting up to 20,000 base units of USDC (0.02 USD, since USDC uses 6 decimals) per call, paid to address `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3` on Base. The payment scheme is "exact" with a 300-second timeout. No OpenAPI schema, 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 additional content.

Capabilities

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

Use cases

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

Fit

Best for

  • —Developers experimenting with x402 payment protocol on Base
  • —Agents needing one-shot paid data retrieval without subscriptions
  • —Low-friction access to transaction receipts with USDC micropayments

Not for

  • —Bulk retrieval of many transaction receipts (single fixed transaction ID)
  • —Users who need detailed API documentation or OpenAPI specs before integrating
  • —Non-crypto users who cannot pay in USDC on Base

Quick start

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

Endpoint

URLhttps://lowpaymentfee.com/api/v1/transactions/87/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, but no OpenAPI schema, no example request/response bodies, and no meaningful documentation were found. The docs/pricing/API pages all render only a wallet-connect prompt. The endpoint path suggests a single fixed resource (transaction 87) rather than a parameterized API, limiting its general utility.

Warnings

  • —No OpenAPI or schema documentation available — endpoint behavior must be inferred from the x402 challenge alone
  • —Docs, pricing, and API pages returned no usable content beyond 'Connect wallet'
  • —Endpoint path is hardcoded to transaction ID 87; unclear if other transaction IDs are available or how to discover them
  • —No example responses available; actual response format is unknown

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-19 13:48:32Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-18
Last seen2026-04-23

Agent access

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