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

What it does

This endpoint at lowpaymentfee.com provides access to a specific transaction receipt (transaction ID 296) 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/296/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 equates to $0.02 per call, consistent with the site's advertised pricing. 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 payment.

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 appears to be a demonstration or early-stage deployment of x402-based API monetization rather than a mature production service.

Capabilities

x402-paymentusdc-basepay-per-requesttransaction-receiptno-api-keyexact-scheme

Use cases

  • —Retrieving a transaction receipt for transaction 296 via programmatic x402 payment
  • —Demonstrating x402 protocol integration for pay-per-request APIs
  • —Agent-driven on-chain payment for API access without API keys

Fit

Best for

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

Not for

  • —Production workloads requiring documented request/response schemas
  • —Users who need free or subscription-based API access
  • —Applications requiring high-throughput or bulk data retrieval

Quick start

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

Endpoint

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

Quality

0.30/ 1.00

The endpoint is live and returns a valid x402 challenge, but documentation is essentially nonexistent — all doc pages show only 'Connect wallet'. There is no OpenAPI spec, no request/response schema, and no examples. The endpoint path suggests a single fixed transaction receipt rather than a general-purpose API. The broader platform lists many endpoints but none are documented beyond a name and price.

Warnings

  • —Documentation pages (/docs, /api, /pricing, /README) contain no substantive content — only 'Connect wallet' prompts.
  • —No OpenAPI spec or request/response schema available for any endpoint.
  • —This specific endpoint (/api/v1/transactions/296/receipt) appears to serve a single fixed transaction receipt (ID 296), not a parameterized resource.
  • —The platform may be a demo or early-stage deployment; production readiness is unclear.
  • —No information on what data the receipt actually contains.

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-19 13:01:15Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-18
Last seen2026-04-24

Agent access

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