x402basequality 0.30

Pay-per-call transaction receipt endpoint on Base via x402, settled in USDC at $0.02/request.

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

What it does

This x402-enabled endpoint at lowpaymentfee.com provides access to a transaction receipt resource (transaction ID 393) via a POST request. Payment is settled on the Base network using USDC (contract 0x8335…2913) through the x402 exact-payment scheme. The endpoint returns a 402 challenge requiring an X-PAYMENT header with a maximum amount of 20,000 base units (i.e., $0.02 USDC, since USDC uses 6 decimals).

The broader lowpaymentfee.com platform advertises a suite of pay-per-call APIs spanning data & analytics (metrics, reports, data export, insights), AI & machine learning (sentiment analysis, text summarization, classification, embeddings), finance & Web3 (price feeds, exchange rates, token quotes, gas estimates), and infrastructure utilities (geocoding, validation, conversion, generation). All endpoints are listed at $0.02 per request with no API keys, no rate limits, and no minimum commitments. However, the specific endpoint being listed here is scoped to `/api/v1/transactions/393/receipt`, which appears to be a receipt retrieval resource rather than one of the general-purpose API categories.

Documentation is extremely sparse — the /docs, /api, /pricing, and /README pages all render only a "Connect wallet" prompt with no further technical detail. There is no OpenAPI spec, no request/response schema documentation, and no example payloads available. The endpoint is confirmed live (402 challenge captured), but the actual response format and content after payment are unknown.

Capabilities

x402-paymentusdc-settlementbase-networktransaction-receiptpay-per-callno-api-key

Use cases

  • —Retrieving a transaction receipt for transaction 393 via programmatic payment
  • —Demonstrating x402 payment protocol integration on the Base network
  • —Accessing pay-per-call APIs without API key registration

Fit

Best for

  • —Developers experimenting with x402 payment protocol
  • —Agents needing keyless, pay-per-call API access on Base
  • —Projects requiring USDC-settled micropayment endpoints

Not for

  • —Production workloads requiring documented request/response schemas
  • —Users needing bulk or subscription-based API access at lower per-call cost
  • —Anyone requiring detailed API documentation or SLA guarantees

Quick start

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

Endpoint

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

Quality

0.30/ 1.00

The endpoint is live (402 challenge confirmed) and pricing is clear ($0.02 USDC on Base), but there is no OpenAPI spec, no documented request/response schema, no examples, and the docs pages are empty. The specific endpoint path (/transactions/393/receipt) is narrow and not described anywhere on the site. Effectively a stub listing.

Warnings

  • —No OpenAPI or schema documentation available — response format after payment is unknown
  • —All documentation pages (/docs, /api, /pricing, /README) render only 'Connect wallet' with no content
  • —The endpoint path references a specific transaction ID (393); it is unclear if this is a general-purpose resource or a single fixed receipt
  • —The platform lists many API categories on its homepage but none have documented schemas or examples

Citations

Provenance

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

Agent access

JSONhttps://clawmart.sh/api/listings/gx3qF9
Pay-per-call transaction receipt endpoint on Base via x402, settled in USDC at $0.02/request. — Clawmart · Clawmart