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 transaction receipt (resource `/api/v1/transactions/354/receipt`) behind an x402 paywall. The endpoint is live and returns a standard x402 challenge requiring payment in USDC on the Base network. The specific resource appears to be one receipt within a broader platform that offers a variety of pay-per-request APIs spanning data analytics, AI/ML inference, finance/Web3 data, and utility services.

The x402 challenge specifies a maxAmountRequired of 20000 base units of USDC (0x8335…2913 on Base). Since USDC uses 6 decimals, this translates to $0.02 per request, consistent with the site's advertised flat pricing of $0.02/request across all endpoints. The platform advertises no API keys, no rate limits, and instant access — payment is handled entirely via the x402 protocol with USDC on Base.

The broader lowpaymentfee.com platform lists 16+ endpoints across four categories: Data & Analytics (metrics, reports, data export, insights), AI & Machine Learning (sentiment analysis, text summarization, classification, embeddings), Finance & Web3 (price feeds, exchange rates, token quotes, gas estimates), and Infrastructure (geocoding, validation, conversion, generation). All are priced at $0.02/request. However, this specific listing is for the transaction receipt endpoint only, and no documentation or schema details were found for any of the endpoints beyond the x402 challenge metadata.

Capabilities

x402-paymentusdc-baseper-call-pricingtransaction-receiptjson-response

Use cases

  • Retrieving a transaction receipt via x402 micropayment
  • Programmatic access to receipt data without API key management
  • Agent-driven payment-gated data retrieval on Base

Fit

Best for

  • Agents that can settle x402 payments in USDC on Base
  • Use cases requiring keyless, pay-per-call API access
  • Developers exploring x402 protocol integrations

Not for

  • Users needing detailed API documentation or OpenAPI schemas before integrating
  • High-volume batch retrieval where per-call costs add up
  • Users without USDC on Base network

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/transactions/354/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, but there is no OpenAPI schema, no documentation, no example request/response bodies, and the specific purpose of 'transaction 354 receipt' is unclear. The crawled docs/pricing/API pages all returned only 'Connect wallet' with no substantive content.

Warnings

  • No API documentation or OpenAPI schema available — endpoint behavior beyond the x402 challenge is unknown.
  • The specific resource '/api/v1/transactions/354/receipt' appears to be a single hardcoded transaction receipt; unclear if this generalizes to other transaction IDs.
  • All documentation pages (docs, api, pricing, README) returned only 'Connect wallet' with no useful content.
  • No example request or response payloads are available to verify what data is actually returned after payment.

Citations

Provenance

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

Agent access