x402basequality 0.30

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

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

What it does

This x402-enabled endpoint at lowpaymentfee.com provides a "Premium API Access" receipt for transaction 193. It is part of a broader platform offering dozens of pay-per-request API endpoints spanning data analytics, AI/ML inference, finance/Web3 data, and infrastructure utilities — all settled on the Base network using USDC at $0.02 per request via the x402 payment protocol.

The specific endpoint `/api/v1/transactions/193/receipt` accepts POST requests and returns JSON. The x402 challenge confirms it is live, requiring a maximum of 20,000 base units of USDC (0.02 USD, since USDC uses 6 decimals) paid to address `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3` on the Base network. The platform advertises no API keys, 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 substantive content. There is no OpenAPI schema, no request/response examples, and no detailed description of what the receipt endpoint actually returns. The broader platform lists many endpoints but provides no documentation for any of them. The exact purpose of a "transaction receipt" in this context is unclear — it could be a blockchain transaction receipt, a payment receipt, or a demo/placeholder endpoint.

Capabilities

x402-paymentusdc-settlementbase-networkpay-per-requestjson-responsetransaction-receipt

Use cases

  • —Retrieving a receipt for transaction 193 via a single paid API call
  • —Demonstrating x402 payment protocol integration for agent-to-API commerce
  • —Programmatic access to transaction data without API key management

Fit

Best for

  • —Developers experimenting with x402 payment protocol on Base
  • —Agents needing keyless, pay-per-call API access settled in USDC
  • —Testing micropayment workflows with low-cost endpoints

Not for

  • —Production use cases requiring documented request/response schemas
  • —Bulk or high-volume data retrieval (no batch endpoints documented)
  • —Users who need detailed API documentation before integrating

Quick start

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

Endpoint

URLhttps://lowpaymentfee.com/api/v1/transactions/193/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 zero documentation on what the endpoint actually returns, no OpenAPI schema, no request/response examples, and all doc pages render only 'Connect wallet'. The specific purpose of a transaction receipt for ID 193 is unexplained.

Warnings

  • —No API documentation available — all doc pages show only 'Connect wallet'
  • —No OpenAPI or request/response schema provided
  • —Purpose of 'transaction 193 receipt' is unclear — may be a demo or placeholder
  • —No information on what the response payload contains
  • —Platform lists many endpoints but documents none of them

Citations

Provenance

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

Agent access

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