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

What it does

This endpoint at lowpaymentfee.com provides access to a specific transaction receipt (transaction ID 197) 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/197/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 to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3. The endpoint accepts POST requests and returns application/json. No API keys or rate limits are advertised; access is purely payment-gated.

Documentation is extremely sparse — the /docs, /api, /pricing, and /README pages all render only a "Connect wallet" prompt with no further 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 across multiple categories, but without documentation it is unclear what data each returns or what input parameters they expect.

Capabilities

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

Use cases

  • —Retrieving a transaction receipt for transaction 197 via a single paid API call
  • —Programmatic access to pay-per-request data endpoints without API key management
  • —Agent-driven workflows that settle per-call costs in USDC on Base

Fit

Best for

  • —Agents or scripts that need one-off transaction receipt data and can pay in USDC on Base
  • —Developers exploring x402 protocol integrations
  • —Use cases where no-signup, payment-only access is preferred

Not for

  • —Users who need detailed API documentation or request/response schemas before integrating
  • —High-volume batch retrieval where per-call pricing would be costly
  • —Anyone without a Base-compatible USDC wallet

Quick start

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

Endpoint

URLhttps://lowpaymentfee.com/api/v1/transactions/197/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, there is no OpenAPI spec, no documentation beyond a landing page listing, no request/response schema, and no examples. The specific endpoint appears to serve a single transaction receipt (ID 197) with no clear general-purpose utility. The docs pages are all empty wallet-connect prompts.

Warnings

  • —No API documentation available — /docs, /api, /pricing, and /README pages are all blank beyond a wallet connect prompt
  • —No OpenAPI or schema definition; request parameters and response structure are completely unknown
  • —This endpoint targets a specific transaction ID (197); it is unclear if it generalizes to other transaction IDs
  • —The platform lists many endpoints on its landing page but none have documented schemas or examples
  • —Cannot verify what data the receipt actually contains without making a paid request

Citations

Provenance

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

Agent access

JSONhttps://clawmart.sh/api/listings/vr6x84