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

What it does

This endpoint at lowpaymentfee.com provides a transaction receipt resource (transaction ID 77) 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 (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, with no API keys, no rate limits, and no minimum commitments required.

The specific endpoint probed (/api/v1/transactions/77/receipt) returns a valid x402 challenge (version 1, scheme "exact") requesting up to 20,000 base units of USDC (0x8335…2913 on Base). Since USDC uses 6 decimals, this translates to $0.02 per call. Payment is sent to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 with a 300-second timeout. The endpoint accepts POST requests and returns application/json.

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 example payloads available. The actual functionality behind this specific receipt endpoint and the broader API suite cannot be verified beyond the landing page descriptions and the live 402 challenge.

Capabilities

x402-paymentusdc-settlementbase-networkpay-per-requesttransaction-receiptno-api-keyjson-response

Use cases

  • —Retrieving transaction receipts via micropayment without API key registration
  • —Programmatic access to pay-per-use data and utility endpoints on Base
  • —Agent-driven workflows that need on-chain payment settlement per API call

Fit

Best for

  • —Developers wanting zero-signup, pay-per-request API access
  • —AI agents with USDC on Base that need low-friction endpoint access
  • —Prototyping x402 payment flows with inexpensive per-call pricing

Not for

  • —Users needing detailed API documentation or OpenAPI specs before integrating
  • —High-volume use cases where $0.02/request adds up without bulk discounts
  • —Users without a Base-compatible USDC wallet

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/transactions/77/receipt
# Returns 402 with x402 challenge; include X-PAYMENT header with signed USDC payment to complete request.

Endpoint

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

Quality

0.30/ 1.00

The endpoint is live and returns a valid x402 challenge with clear pricing ($0.02 USDC on Base). However, there is no OpenAPI spec, no request/response schema, no documentation beyond a landing page, and no examples. The specific purpose of the 'transactions/77/receipt' resource is unclear. This is effectively a stub listing.

Warnings

  • —No OpenAPI specification or schema documentation available
  • —All documentation pages (/docs, /api, /pricing, /README) render only 'Connect wallet' with no content
  • —The specific functionality of /api/v1/transactions/77/receipt is undocumented — unclear what the receipt contains
  • —The broader API suite (AI, analytics, finance, utils) is advertised but none of those endpoints were probed
  • —No request body schema or response schema is documented anywhere

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-19 13:53:41Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-18
Last seen2026-04-23

Agent access

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