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 a transaction receipt resource (transaction ID 107) behind an x402 paywall. It is part of a broader platform that offers a variety of pay-per-request APIs spanning data analytics, AI/ML inference, finance/Web3 data, and infrastructure utilities — all priced at $0.02 per call and settled in USDC on the Base network.

The specific endpoint `/api/v1/transactions/107/receipt` accepts POST requests and returns JSON. Payment is handled via the x402 protocol: callers must include an `X-PAYMENT` header containing a signed payment of up to 20,000 base units of USDC (0.02 USD, since USDC uses 6 decimals) to the merchant address `0x1A2B…85F3`. The payment scheme is "exact" with a 300-second timeout window. No API keys or rate limits are advertised; access is gated purely by micropayment.

Documentation on the site is extremely thin — 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 usage examples available. The endpoint is confirmed live (returns a proper 402 challenge), but the actual content and structure of the receipt response are unknown.

Capabilities

x402-paymentusdc-micropaymentbase-networktransaction-receiptpay-per-requestno-api-key

Use cases

  • Retrieving a transaction receipt for transaction 107 via micropayment
  • Programmatic access to receipt data without API key management
  • Agent-driven payment-gated data retrieval on Base

Fit

Best for

  • Developers experimenting with x402 micropayment protocols
  • Agents that need to fetch transaction receipts on-demand
  • Use cases requiring keyless, pay-per-call API access

Not for

  • Bulk retrieval of many transaction receipts (no batch endpoint documented)
  • Users who need detailed API documentation or response schemas before integrating

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/transactions/107/receipt
# Returns 402 with x402 challenge; include X-PAYMENT header with signed USDC payment (0.02 USD on Base) to access.

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.30/ 1.00

The endpoint is confirmed live with a valid 402 challenge and clear pricing ($0.02 USDC on Base). However, there is no OpenAPI spec, no request/response schema, no documentation beyond a wallet-connect prompt, and the actual purpose of the receipt content is undocumented. This is effectively a stub listing.

Warnings

  • No API documentation available — docs, pricing, and README pages only show 'Connect wallet'
  • No OpenAPI or output schema provided; response format is unknown
  • The specific endpoint is for a single transaction ID (107); unclear if other transaction IDs are available or how they are discovered
  • The broader platform advertises many API categories (AI, analytics, finance, utilities) but none have documented schemas

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-19 11:51:03Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-18
Last seen2026-04-25

Agent access