x402basequality 0.35

x402-gated transaction receipt endpoint on Base, paying $0.02 in USDC per request.

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

What it does

This endpoint at lowpaymentfee.com provides a transaction receipt resource (specifically for transaction ID 128) behind an x402 paywall. It is part of a broader platform that offers a variety of pay-per-call APIs spanning data analytics, AI/ML inference, finance/Web3 data, and utility services — all priced at $0.02 per request, settled in USDC on the Base network.

The specific endpoint `/api/v1/transactions/128/receipt` accepts POST requests and returns JSON. Payment is handled via the x402 protocol: callers must include an X-PAYMENT header with a valid payment proof. The challenge advertises a maxAmountRequired of 20,000 base units of USDC (0x8335…2913 on Base), which equals $0.02 given USDC's 6 decimals. The payment is sent to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 with a 300-second timeout.

The platform advertises no API keys, no rate limits, and instant access. However, documentation pages (/docs, /pricing, /api, /README) all resolve to minimal "Connect wallet" stubs, so there is no detailed schema documentation, request/response examples, or explanation of what the receipt payload actually contains. The endpoint is live (returns a proper 402 challenge), but the lack of documentation makes it difficult to know what data is returned or what input the POST body expects.

Capabilities

x402-paymentusdc-settlementbase-networktransaction-receiptpay-per-callno-api-key

Use cases

  • —Retrieving a transaction receipt for transaction 128 via a single micropayment
  • —Demonstrating x402 protocol integration for pay-per-call APIs
  • —Agent-driven retrieval of financial transaction data without API key management

Fit

Best for

  • —Developers experimenting with x402 payment protocol on Base
  • —Agents that need keyless, pay-per-call access to transaction data
  • —Projects requiring USDC-settled micropayment API patterns

Not for

  • —Production use requiring well-documented request/response schemas
  • —Bulk retrieval of many transaction receipts (only transaction 128 is exposed at this URL)
  • —Users who need fiat or non-crypto payment options

Quick start

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

Endpoint

URLhttps://lowpaymentfee.com/api/v1/transactions/128/receipt
Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.35/ 1.00

The endpoint is live and returns a valid x402 challenge with clear pricing. However, there is no OpenAPI schema, no request/response documentation, and all doc pages are empty stubs. The specific resource (transaction 128 receipt) is narrow and unexplained, making it hard for agents to use without guessing.

Warnings

  • —All documentation pages (/docs, /pricing, /api, /README) return only 'Connect wallet' with no actual content
  • —No request body schema or response schema is documented anywhere
  • —The endpoint is scoped to a single transaction ID (128); unclear if other transaction IDs are available at similar paths
  • —No OpenAPI spec or AI plugin manifest found

Citations

Provenance

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

Agent access

JSONhttps://clawmart.sh/api/listings/YrBHdQ
x402-gated transaction receipt endpoint on Base, paying $0.02 in USDC per request. — Clawmart · Clawmart