x402basequality 0.35

x402-gated transaction receipt endpoint on Base, paying $0.02 in USDC per request.

Price
0.02 USDC / call
Protocol
x402
Verified
no

What it does

This endpoint at lowpaymentfee.com provides a transaction receipt resource behind an x402 paywall. It is part of a broader platform that offers a variety of pay-per-request APIs spanning data analytics, AI/ML inference, finance/Web3 data, and infrastructure utilities — all priced at $0.02 per call and settled in USDC on the Base network.

The specific endpoint `/api/v1/transactions/109/receipt` returns a JSON response upon payment. The x402 challenge advertises a maxAmountRequired of 20,000 base units of USDC (0x8335… on Base), which equals $0.02 given USDC's 6 decimals. Payment is made via the x402 exact scheme with no API keys or rate limits required. The platform emphasizes simplicity: no subscriptions, no commitments, just per-call micropayments.

Documentation on the site 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 examples of what the receipt payload actually contains. The endpoint is confirmed live (402 challenge captured), but the lack of documentation makes it difficult to know what data is returned or what inputs (if any) the POST body expects.

Capabilities

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

Use cases

  • Retrieving a transaction receipt for transaction ID 109 via micropayment
  • Programmatic access to receipt data without API key registration
  • Agent-driven workflows that need on-chain-settled per-call billing

Fit

Best for

  • Developers wanting zero-signup, pay-per-use API access
  • AI agents with x402 payment capability on Base
  • Users who prefer USDC micropayments over subscription billing

Not for

  • Users needing detailed API documentation or OpenAPI specs before integrating
  • Bulk/high-volume use cases where per-call pricing may add up
  • Anyone without a Base-compatible USDC wallet

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/transactions/109/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 confirmed live with a valid x402 402 challenge and clear pricing ($0.02 USDC on Base). However, there is no OpenAPI spec, no documentation beyond a landing page listing, no request/response schema, and no examples. The specific purpose of this receipt endpoint is unclear beyond its URL path. Effectively a stub listing.

Warnings

  • No OpenAPI or schema documentation available — request body and response format are unknown
  • All documentation pages (/docs, /api, /pricing, /README) render only 'Connect wallet' with no content
  • The specific data returned by the /transactions/109/receipt endpoint is undocumented
  • The endpoint path includes a hardcoded transaction ID (109), suggesting it may be a single-resource endpoint rather than a general-purpose API

Citations

Provenance

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

Agent access