x402basequality 0.35

Pay-per-call transaction receipt endpoint on Base via x402, settled in USDC at $0.02/request.

Price
0.02 USDC / call
Protocol
x402
Verified
no

What it does

This x402-enabled endpoint at lowpaymentfee.com provides a transaction receipt retrieval API. The specific resource `/api/v1/transactions/199/receipt` returns receipt data for transaction ID 199 in JSON format. Payment is handled inline via the x402 protocol: callers attach a USDC payment on the Base network in the `X-PAYMENT` header, and the endpoint returns the receipt data upon successful settlement.

The endpoint is part of a broader platform (lowpaymentfee.com) that offers multiple pay-per-call API categories including 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 on the platform are priced at $0.02 per request with no API keys, no rate limits, and no minimum commitments.

The x402 challenge for this specific endpoint advertises a `maxAmountRequired` of 20,000 base units of USDC (contract `0x8335...2913` on Base), which equals $0.02 given USDC's 6 decimals. The payment scheme is "exact" with a 300-second timeout. No OpenAPI spec or detailed documentation was found beyond the landing page listings; the docs, API, pricing, and README pages all returned only a wallet-connect prompt with no substantive content.

Capabilities

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

Use cases

  • Retrieving transaction receipt data on a per-call payment basis
  • Integrating pay-per-use API access into agent workflows without API key management
  • Programmatic access to transaction records settled via USDC on Base

Fit

Best for

  • Agents or applications needing keyless, pay-per-call API access
  • Developers who want to avoid subscription commitments for occasional API calls
  • Crypto-native workflows already operating on the Base network

Not for

  • High-volume use cases where per-call pricing may add up versus flat-rate plans
  • Users without access to USDC on the Base network for payment

Quick start

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

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.35/ 1.00

The endpoint is live (402 challenge captured) and pricing is clear ($0.02 USDC on Base), but there is no OpenAPI schema, no documented request/response format, no examples, and all documentation pages return only a wallet-connect prompt. The specific purpose of this particular receipt endpoint is unclear beyond the generic title.

Warnings

  • No OpenAPI or schema documentation available — request and response formats are unknown
  • All doc/pricing/README pages return only a wallet-connect prompt with no substantive content
  • The endpoint path references a specific transaction ID (199); it is unclear whether this is a generic pattern or a fixed resource
  • No examples of successful responses are available

Citations

Provenance

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

Agent access