x402basequality 0.30

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
Endpoint
https://lowpaymentfee.com/api/v1/transactions/247/receipt

What it does

This x402-enabled endpoint at lowpaymentfee.com provides access to a transaction receipt resource (transaction ID 247) via a POST request. Payment is settled on the Base network using USDC (contract 0x8335…2913) through the x402 exact payment scheme. The per-request cost is $0.02 (20,000 base units of USDC with 6 decimals).

The provider's landing page advertises a broader suite of APIs spanning 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 utilities (geocoding, validation, conversion, generation) — all priced uniformly at $0.02 per request with no API keys, no rate limits, and no minimum commitments. However, this specific listing covers only the `/api/v1/transactions/247/receipt` endpoint.

Documentation is extremely sparse: the docs, API, pricing, and README pages all render only a "Connect wallet" prompt with no further technical detail. There is no OpenAPI spec, no request/response schema documentation, and no example payloads available. The endpoint is confirmed live — it returns a proper x402 402 challenge — but without documentation it is unclear what request body (if any) is expected or what the receipt response structure looks like.

Capabilities

x402-paymentusdc-settlementbase-networktransaction-receiptpay-per-callno-api-key

Use cases

  • —Retrieving a transaction receipt for transaction 247 via a single paid API call
  • —Demonstrating x402 payment protocol integration with USDC on Base
  • —Agent-driven pay-per-call access to financial transaction data without API key management

Fit

Best for

  • —Developers experimenting with x402 protocol payments
  • —AI agents needing keyless, pay-per-call API access
  • —Applications requiring on-chain USDC micropayment settlement on Base

Not for

  • —Production workloads requiring documented request/response schemas
  • —Bulk or high-volume transaction receipt retrieval (no batch endpoint documented)
  • —Users who need fiat-only payment rails

Quick start

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

Endpoint

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

Quality

0.30/ 1.00

The endpoint is live and returns a valid x402 402 challenge with clear pricing, but there is no OpenAPI spec, no request/response schema, no documentation beyond a wallet-connect prompt, and no example payloads. 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 technical content
  • —This endpoint is for a specific transaction ID (247); it is unclear whether other transaction IDs are available or how they are discovered
  • —The broader API suite advertised on the landing page is not verified — only this single endpoint was probed

Citations

Provenance

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

Agent access

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