x402basequality 0.35

Transaction receipt retrieval via x402 micropayment on Base network for $0.02 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 361) behind an x402 paywall. The site operates a broad suite of pay-per-call APIs spanning data analytics, AI/ML inference, finance/Web3 data, and infrastructure utilities — all priced at $0.02 per request and settled in USDC on the Base network. No API keys, rate limits, or subscriptions are required; callers simply attach an x402 payment header to each request.

The specific endpoint `/api/v1/transactions/361/receipt` is labeled "Premium API Access" and accepts POST requests. It returns application/json content. The x402 challenge advertises a maxAmountRequired of 20,000 base units of USDC (0x8335…2913 on Base), which equals $0.02 given USDC's 6 decimals. Payment is sent to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 using the "exact" scheme with a 300-second timeout.

Documentation on the site 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 live (returns a proper 402 challenge), but the actual data returned after payment is unknown from the available material.

Capabilities

x402-paymentusdc-basepay-per-requesttransaction-receiptjson-responseno-api-keyno-rate-limit

Use cases

  • Retrieving transaction receipt data for a specific transaction via micropayment
  • Programmatic access to receipt information without API key management
  • Agent-driven workflows that need on-demand paid data retrieval

Fit

Best for

  • Developers wanting zero-signup, pay-per-call API access
  • AI agents that can settle x402 payments in USDC on Base
  • Use cases requiring no rate limits or subscription commitments

Not for

  • Users who need detailed API documentation or OpenAPI specs before integrating
  • Bulk retrieval of many different transaction receipts (only resource 361 is exposed at this endpoint)
  • Non-crypto payment workflows — requires USDC on Base network

Quick start

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

Endpoint

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 there is no documentation, no OpenAPI spec, no request/response schema, and no examples. The purpose of the specific receipt endpoint is unclear beyond its generic label. Effectively a stub listing.

Warnings

  • No API documentation available — /docs, /api, /pricing, and /README pages all show only 'Connect wallet' with no content
  • No OpenAPI or schema definition found for request or response payloads
  • The actual data returned by this endpoint after payment is completely undocumented
  • This is a single resource-specific endpoint (/transactions/361/receipt); it is unclear whether other transaction IDs are accessible or what 'Premium API Access' specifically provides

Citations

Provenance

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

Agent access