x402basequality 0.35

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

Price
0.02 USDC / call
Protocol
x402
Verified
no

What it does

This endpoint at lowpaymentfee.com provides a transaction receipt retrieval service behind an x402 paywall. It is part of a broader platform offering multiple API categories including Data & Analytics, AI & Machine Learning, Finance & Web3, and Infrastructure utilities—all priced at $0.02 per request with no API keys, no rate limits, and no commitments required.

The specific endpoint `/api/v1/transactions/274/receipt` accepts POST requests and returns JSON. Payment is settled on the Base network using USDC (contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) at a cost of 20,000 base units (i.e., $0.02 given USDC's 6 decimals). The x402 challenge confirms the endpoint is live and uses the "exact" payment scheme with a 300-second timeout.

The platform's documentation pages are sparse—most routes simply show a "Connect wallet" prompt with no further technical detail. There is no OpenAPI spec, no example request/response payloads, and no description of what the receipt object contains. The endpoint path suggests it retrieves a receipt for a specific transaction (ID 274), but it is unclear whether this is a fixed resource or a parameterized pattern.

Capabilities

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

Use cases

  • Retrieving a transaction receipt after a payment event
  • Programmatic verification of transaction completion
  • Agent-driven workflows that need proof-of-payment documents

Fit

Best for

  • Agents needing instant access without API key registration
  • Low-volume, pay-as-you-go transaction verification
  • Crypto-native workflows on Base L2

Not for

  • High-volume batch processing where per-call fees add up
  • Users who need detailed API documentation before integrating
  • Non-crypto users without a Base-compatible wallet

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/transactions/274/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 confirmed live via a valid 402 challenge with clear pricing and network details, but there is no OpenAPI spec, no documentation of request/response schemas, and the docs pages are empty. The specific purpose of this receipt endpoint is unclear.

Warnings

  • No OpenAPI or schema documentation available
  • All documentation pages return only 'Connect wallet' with no technical content
  • Unclear what the receipt response body contains
  • Endpoint path includes a hardcoded transaction ID (274); unclear if this is parameterized or fixed
  • Platform appears to be a demo or early-stage service with minimal real documentation

Citations

Provenance

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

Agent access

Pay-per-call transaction receipt endpoint on Base via x402, $0.02 per request in USDC. — Clawmart · Clawmart