x402basequality 0.30

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

Price
0.02 USDC / call
Protocol
x402
Verified
no

What it does

This endpoint at lowpaymentfee.com provides access to a specific transaction receipt (transaction ID 83) behind an x402 paywall. The broader lowpaymentfee.com platform advertises a suite of pay-per-request APIs spanning data & analytics, AI & machine learning (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.

The specific endpoint probed — `/api/v1/transactions/83/receipt` — returned a valid x402 challenge with a `maxAmountRequired` of 20,000 base units of USDC (0x8335… on Base). Since USDC uses 6 decimals, this translates to $0.02 per call, consistent with the site's advertised pricing. Payment is made via the x402 "exact" scheme to the specified payTo address. The endpoint accepts POST requests and returns application/json.

Documentation on the site is extremely thin — 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 usage examples available. The nature of what the "transaction receipt" contains is not documented, making it difficult to assess the endpoint's practical utility without making a paid request.

Capabilities

x402-paymentusdc-settlementbase-networkper-call-pricingtransaction-receiptjson-responseno-api-key

Use cases

  • Retrieving a transaction receipt for transaction 83 via a single paid API call
  • Demonstrating x402 payment protocol integration for agent-to-agent commerce
  • Testing micropayment flows on the Base L2 network

Fit

Best for

  • Developers experimenting with x402 payment protocol
  • Agents needing pay-per-call API access without API key management
  • Low-cost micropayment API consumption on Base

Not for

  • Production workloads requiring documented request/response schemas
  • Bulk data retrieval or high-throughput analytics
  • Users who need detailed API documentation before purchasing

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/transactions/83/receipt
# Returns 402 with x402 challenge; attach X-PAYMENT header with valid USDC payment on Base to access the receipt.

Endpoint

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 documentation, no OpenAPI spec, no request/response examples, and the purpose of this specific transaction receipt endpoint is unclear. The broader site lists many APIs but provides zero documentation beyond titles and prices.

Warnings

  • No API documentation available — docs, pricing, and README pages all show only 'Connect wallet'
  • No OpenAPI or schema definition for request or response payloads
  • The specific purpose and contents of the transaction 83 receipt are undocumented
  • Cannot verify what data is actually returned without making a paid request

Citations

Provenance

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

Agent access