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/118/receipt

What it does

This endpoint at lowpaymentfee.com provides a transaction receipt resource (transaction ID 118) 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 and settled in USDC on the Base network.

The specific endpoint `/api/v1/transactions/118/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 timeout of 300 seconds.

The platform advertises no API keys, no rate limits, and instant access. Documentation pages (/docs, /pricing, /api) appear to require a wallet connection and contain no additional readable content. There is no OpenAPI schema, no detailed request/response documentation, and no examples of what the receipt payload actually contains. The endpoint is confirmed live (402 challenge returned successfully).

Capabilities

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

Use cases

  • —Retrieving a transaction receipt for transaction 118 via a micropayment-gated API
  • —Demonstrating x402 protocol integration for pay-per-call services
  • —Accessing financial or transactional data without traditional API key registration

Fit

Best for

  • —Developers experimenting with x402 protocol payments
  • —Agents that can settle USDC on Base for per-call API access
  • —Use cases requiring keyless, pay-as-you-go API access

Not for

  • —Users who need detailed API documentation or OpenAPI specs before integrating
  • —High-volume batch retrieval where per-call pricing is inefficient
  • —Users without a Base-compatible USDC wallet

Quick start

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

Endpoint

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

Quality

0.35/ 1.00

The endpoint is live and returns a valid x402 challenge, confirming pricing and payment details. However, there is no OpenAPI schema, no request/response examples, and the docs/pricing/api pages are empty (wallet-gated). The specific purpose of this receipt endpoint is unclear beyond its URL path. Effectively a stub listing.

Warnings

  • —No OpenAPI or schema documentation available — request and response formats are unknown
  • —Documentation pages (/docs, /pricing, /api, /README) all require wallet connection and provide no readable content
  • —The specific data returned by the /transactions/118/receipt endpoint is undocumented
  • —The broader platform lists many endpoints but none have detailed documentation visible without wallet connection

Citations

Provenance

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

Agent access

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