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/307/receipt

What it does

This x402-enabled endpoint at lowpaymentfee.com provides a transaction receipt for transaction ID 307 via a POST request. It is part of a broader platform offering multiple API categories — data & analytics, AI & machine learning, finance & Web3, and infrastructure utilities — all priced at $0.02 per request with no API keys, no rate limits, and no commitments required.

The specific endpoint `/api/v1/transactions/307/receipt` returns a JSON response and accepts payment in USDC on the Base network using the x402 exact payment scheme. The max amount required is 20,000 base units of USDC (6 decimals), which equals $0.02. Payment is sent to address `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3` with a timeout of 300 seconds.

The platform advertises a wide range of endpoints across categories including sentiment analysis, text summarization, classification, embeddings, price feeds, exchange rates, geocoding, validation, and more — all at the same $0.02 per-call price point. However, 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 usage examples available. The exact nature of the data returned by this receipt endpoint is unclear beyond the MIME type being `application/json`.

Capabilities

x402-paymentusdc-settlementbase-networkper-call-pricingtransaction-receiptjson-response

Use cases

  • —Retrieving a transaction receipt for transaction 307 via programmatic pay-per-call access
  • —Demonstrating x402 payment protocol integration on the Base network
  • —Agent-driven micropayment workflows that need no API keys or accounts

Fit

Best for

  • —Developers experimenting with x402 payment protocol
  • —Agents needing keyless, pay-per-call API access on Base
  • —Micropayment use cases where $0.02/call pricing is attractive

Not for

  • —Production workloads requiring detailed API documentation and SLAs
  • —Bulk data retrieval where per-call pricing would be cost-prohibitive
  • —Users who need fiat-only payment options

Quick start

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

Endpoint

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

Quality

0.30/ 1.00

The endpoint is live (returns 402 with a valid x402 challenge), and pricing is clear at $0.02 USDC on Base. However, there is no OpenAPI spec, no request/response schema, no documentation beyond a wallet-connect prompt, and the specific purpose of this receipt endpoint is unclear. The platform lists many endpoints but provides no technical details for any of them.

Warnings

  • —No OpenAPI or schema documentation available for any endpoint on the platform
  • —Docs, API, pricing, and README pages all render only 'Connect wallet' with no content
  • —The specific purpose and response format of the /transactions/307/receipt endpoint is undocumented
  • —The hardcoded transaction ID (307) in the URL suggests this may be a single-resource endpoint rather than a parameterized API
  • —No examples of request body or response body are available

Citations

Provenance

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

Agent access

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