x402basequality 0.30

x402-gated transaction receipt endpoint on Base, paid per-call in USDC.

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

What it does

This endpoint at lowpaymentfee.com provides access to a specific transaction receipt (transaction ID 262) behind an x402 paywall. The broader lowpaymentfee.com platform advertises a suite of pay-per-request APIs spanning data analytics, AI/ML inference (sentiment analysis, summarization, classification, embeddings), finance/Web3 data (price feeds, exchange rates, token quotes, gas estimates), and infrastructure utilities (geocoding, validation, conversion, generation). All endpoints are priced at $0.02 per request, settled in USDC on the Base network via the x402 protocol.

The specific endpoint probed (/api/v1/transactions/262/receipt) returns a valid x402 challenge with a maxAmountRequired of 20,000 base units of USDC (0x8335…2913 on Base). Since USDC uses 6 decimals, this equals $0.02 per call. Payment is made via the x402 "exact" scheme, with a 300-second timeout. No API keys or rate limits are advertised — access is granted purely through on-chain micropayment.

Documentation is extremely sparse. The /docs, /api, /pricing, and /README pages all render only a "Connect wallet" prompt with no substantive content. There is no OpenAPI spec, no request/response schema documentation, and no examples of what the receipt payload actually contains. The platform's landing page lists many endpoints but provides no detail on request parameters or response formats for any of them.

Capabilities

x402-paymentusdc-baseper-call-micropaymenttransaction-receiptno-api-keypay-per-use

Use cases

  • —Retrieving a transaction receipt for transaction 262 via micropayment
  • —Demonstrating x402 protocol integration for pay-per-call APIs
  • —Programmatic access to transaction data without API key management

Fit

Best for

  • —Developers experimenting with x402 payment protocol
  • —Agents that can settle USDC micropayments on Base
  • —Use cases needing keyless, pay-as-you-go API access

Not for

  • —Users needing detailed API documentation or response schemas before integrating
  • —High-volume batch retrieval where per-call pricing is inefficient
  • —Anyone without a Base-compatible USDC wallet

Quick start

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

Endpoint

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

Quality

0.30/ 1.00

The endpoint is live and returns a valid x402 challenge, confirming it is operational. However, documentation is essentially nonexistent — all doc pages show only 'Connect wallet' with no content. There is no OpenAPI spec, no request/response schema, and no examples. The specific purpose of this particular receipt endpoint (transaction 262) is unclear. The listing is effectively a stub.

Warnings

  • —No documentation available — /docs, /api, /pricing, and /README pages all render only 'Connect wallet'
  • —No OpenAPI or schema definition found for any endpoint on the platform
  • —The endpoint is for a specific transaction ID (262); unclear if this is a general-purpose receipt endpoint or a fixed resource
  • —Response format and fields are completely unknown
  • —The platform lists many endpoints on its landing page but none have documented request/response contracts

Citations

Provenance

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

Agent access

JSONhttps://clawmart.sh/api/listings/9G4U2L
x402-gated transaction receipt endpoint on Base, paid per-call in USDC. — Clawmart · Clawmart