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

What it does

This endpoint at lowpaymentfee.com provides access to a transaction receipt (resource ID 148) behind an x402 paywall. The site advertises itself as a platform hosting multiple pay-per-request 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/148/receipt` returns a JSON response upon payment. The x402 challenge confirms the endpoint is live, accepting POST requests, and requires a maximum of 20,000 base units of USDC (0x8335…2913 on Base, 6 decimals = $0.02) paid to address 0x1A2B…85F3. The payment scheme is "exact" with a 300-second timeout. No API keys or rate limits are advertised; access is granted purely through the x402 payment protocol.

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 spec, no request/response schema documentation, and no examples of what the receipt payload actually contains. The site lists many other endpoints across analytics, AI, finance, and utility categories, but this listing covers only the `/api/v1/transactions/148/receipt` resource. Without documentation on the response format or the nature of "transaction 148," the practical utility of this specific endpoint is unclear.

Capabilities

x402-paymentusdc-settlementbase-networktransaction-receiptpay-per-requestno-api-keyjson-response

Use cases

  • Retrieving a transaction receipt for resource ID 148 via programmatic x402 payment
  • Demonstrating x402 protocol integration with USDC on Base
  • Agent-driven pay-per-request data retrieval without API key management

Fit

Best for

  • Developers experimenting with x402 payment protocol on Base
  • Agents that need keyless, pay-per-call API access
  • Testing USDC micropayment flows

Not for

  • Production use cases requiring documented response schemas
  • Bulk or high-volume data retrieval where per-request pricing is inefficient
  • Users who need detailed API documentation before integrating

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/transactions/148/receipt
# Returns 402 with x402 challenge; attach X-PAYMENT header with USDC payment proof to access the receipt.

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.30/ 1.00

The endpoint is live and returns a valid x402 challenge with clear pricing, but there is no documentation, no OpenAPI spec, no response schema, and no explanation of what the receipt contains. The docs pages are empty stubs. This is effectively a stub listing.

Warnings

  • No documentation available — /docs, /api, /pricing, and /README pages all show only 'Connect wallet' with no content
  • No OpenAPI or schema describing the response payload
  • The nature of 'transaction 148' and what the receipt contains is completely undocumented
  • No agents.txt present
  • Multiple other endpoints listed on the site are not covered by this listing

Citations

Provenance

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

Agent access