x402basequality 0.30

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

What it does

This endpoint at lowpaymentfee.com provides a transaction receipt resource (transaction ID 211) behind an x402 paywall. It is part of a broader platform that advertises multiple API categories including Data & Analytics, AI & Machine Learning, Finance & Web3, and Infrastructure utilities — all priced at $0.02 per request, settled in USDC on the Base network.

The specific endpoint `/api/v1/transactions/211/receipt` accepts POST requests and returns `application/json`. Payment is handled via the x402 protocol: callers receive a 402 challenge containing the accepted payment scheme (exact), the USDC asset contract on Base (`0x8335…`), and a maximum amount of 20,000 base units (i.e., $0.02 given USDC's 6 decimals). No API keys are required; access is granted per-request upon valid payment. The platform advertises no rate limits and instant access.

Documentation is extremely sparse — 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 beyond the x402 challenge's `outputSchema`, and no explanation of what the receipt payload actually contains. The platform lists many other endpoints across analytics, AI, finance, and utility categories, but this listing covers only the `/api/v1/transactions/211/receipt` resource.

Capabilities

x402-paymentusdc-basetransaction-receiptper-request-billingno-api-key

Use cases

  • —Retrieving a receipt for a specific transaction (ID 211) via programmatic payment
  • —Demonstrating x402 protocol integration for per-request micropayments
  • —Agents that need to fetch financial transaction records without pre-registration

Fit

Best for

  • —Developers experimenting with x402 pay-per-request protocols
  • —Agents needing keyless, on-demand API access settled in USDC on Base
  • —Prototyping micropayment-gated API workflows

Not for

  • —Production use requiring documented request/response schemas
  • —Bulk retrieval of many transaction receipts (each call costs $0.02 with no batch endpoint documented)
  • —Users who need detailed API documentation before integrating

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/transactions/211/receipt
# Returns 402 with x402 challenge; include X-PAYMENT header with valid USDC payment to receive the receipt.

Endpoint

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

Quality

0.30/ 1.00

The endpoint is live and returns a valid x402 challenge, but documentation is effectively nonexistent — all doc pages show only 'Connect wallet'. There is no OpenAPI spec, no request/response schema, and no explanation of what the receipt payload contains. The endpoint path is specific to a single transaction ID (211), making its general utility unclear.

Warnings

  • —Documentation pages (/docs, /api, /pricing, /README) contain no usable content — only a 'Connect wallet' prompt.
  • —No OpenAPI or schema describing the receipt response body.
  • —Endpoint is scoped to a single transaction ID (211); unclear if this is a demo or a real resource.
  • —The broader platform lists many endpoints (AI, analytics, finance, utils) but none have documented schemas.

Citations

Provenance

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

Agent access

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