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 a transaction receipt resource (transaction ID 164) 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, with no API keys, no rate limits, and no minimum commitments.

The specific endpoint probed — `/api/v1/transactions/164/receipt` — returns a valid x402 challenge (HTTP 402) requesting up to 20,000 base units of USDC (0.02 USDC, i.e., $0.02) on Base. Payment is made via the x402 "exact" scheme to the specified wallet address. The response MIME type is `application/json` and the endpoint accepts POST requests. No OpenAPI schema, detailed documentation, or example responses were found in the crawl; the docs, pricing, and API pages all rendered only a "Connect wallet" prompt with no further content.

Because the crawled documentation pages are essentially empty beyond the landing page listing, the actual behavior and response schema of this endpoint (and the platform's other endpoints) remain unverified. The platform appears to be a demonstration or early-stage x402 API marketplace. Users should be aware that no detailed API documentation, error handling guidance, or response schemas are publicly available.

Capabilities

x402-paymentusdc-settlementbase-networkper-request-pricingtransaction-receiptjson-responsepost-method

Use cases

  • Retrieving a transaction receipt for transaction 164 via a single micropayment
  • Demonstrating x402 protocol payment flows on Base
  • Programmatic access to paid API resources without API key management

Fit

Best for

  • Developers experimenting with x402 payment protocol
  • Agents that can settle USDC payments on Base for per-call API access
  • Use cases requiring keyless, pay-as-you-go API consumption

Not for

  • Production workloads requiring documented and stable API contracts
  • Users who need detailed response schemas or error documentation before integrating
  • High-volume use cases where per-request crypto settlement overhead is impractical

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/transactions/164/receipt
# Returns HTTP 402 with x402 challenge.
# Include X-PAYMENT header with a valid x402 payment proof (USDC on Base, $0.02) to receive the receipt.

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.30/ 1.00

The endpoint is live and returns a well-formed x402 challenge, but there is no OpenAPI schema, no documentation beyond a landing page listing, no example responses, and no description of what the receipt actually contains. The docs/pricing/API pages are all blank beyond a wallet-connect prompt. This is effectively a stub listing.

Warnings

  • No API documentation available — docs, pricing, and API pages render only a 'Connect wallet' prompt with no content.
  • No OpenAPI or output schema provided; the actual response payload structure is unknown.
  • The specific endpoint is for a single transaction receipt (ID 164); unclear if this is a general-purpose API or a fixed demo resource.
  • Platform appears to be early-stage or a demonstration; reliability and longevity are unverified.

Citations

Provenance

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

Agent access