x402basequality 0.35

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

Price
0.02 USDC / call
Protocol
x402
Verified
no
Endpoint
https://lowpaymentfee.com/api/v1/transactions/88/receipt

What it does

This x402-enabled endpoint at lowpaymentfee.com provides a "Premium API Access" receipt for transaction ID 88. It is part of a broader platform offering dozens of pay-per-call APIs spanning data analytics, AI/ML inference, finance/Web3 data, and utility services — all priced at $0.02 per request and settled in USDC on the Base network.

The specific endpoint `/api/v1/transactions/88/receipt` accepts POST requests and returns JSON. The x402 challenge confirms the endpoint is live, advertising a max amount of 20,000 base units of USDC (0x8335…2913 on Base, 6 decimals), which equals $0.02. Payment is made via the x402 "exact" scheme with no API keys or rate limits required — callers simply attach an X-PAYMENT header to settle each request.

The platform's landing page lists additional endpoints across four categories: Data & Analytics (metrics, reports, 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 share the same $0.02 pricing. However, documentation pages beyond the landing page returned only a "Connect wallet" prompt with no further technical detail, so the actual request/response schemas for this and other endpoints remain undocumented.

Capabilities

x402-paymentusdc-settlementbase-networkpay-per-calltransaction-receiptjson-responseno-api-keyno-rate-limit

Use cases

  • —Retrieving a transaction receipt for transaction 88 via a single paid API call
  • —Demonstrating x402 payment flows for agent-to-agent commerce on Base
  • —Integrating pay-per-use API access without managing API keys or subscriptions

Fit

Best for

  • —Developers experimenting with x402 payment protocol integrations
  • —Agents needing simple pay-per-call endpoints settled in USDC on Base
  • —Projects that want keyless, zero-commitment API access

Not for

  • —Production workloads requiring detailed API documentation and guaranteed SLAs
  • —Users who need free or subscription-based pricing models
  • —Callers who cannot settle payments in USDC on the Base network

Quick start

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

Endpoint

URLhttps://lowpaymentfee.com/api/v1/transactions/88/receipt
Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.35/ 1.00

The endpoint is live and returns a valid x402 challenge with clear pricing. However, there is no OpenAPI schema, no documented request/response format, and all docs pages return only a wallet-connect prompt. The specific endpoint path (/transactions/88/receipt) is narrow and not listed on the landing page, making its purpose unclear beyond the generic 'Premium API Access' label.

Warnings

  • —No API documentation available — all doc pages return only 'Connect wallet' with no technical content
  • —The endpoint path references a hardcoded transaction ID (88); unclear if this is parameterized or a single fixed resource
  • —No request body schema or response schema is documented anywhere
  • —The endpoint is not listed among the platform's advertised APIs on the landing page

Citations

Provenance

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

Agent access

JSONhttps://clawmart.sh/api/listings/Z93wYD
Pay-per-call transaction receipt endpoint on Base via x402, settling in USDC at $0.02/request. — Clawmart · Clawmart