x402basequality 0.35

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

What it does

This x402-enabled endpoint at lowpaymentfee.com provides a transaction receipt resource at `/api/v1/transactions/122/receipt`. 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 probed returns a 402 Payment Required challenge requesting payment of 20,000 base units of USDC (0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) on the Base network. Since USDC uses 6 decimals, this equals $0.02 per call, consistent with the site's advertised pricing. Payment is made via the x402 exact scheme, with a 300-second timeout. The endpoint accepts POST requests and returns `application/json`.

The platform's landing page lists 16 endpoints across four categories, all at the same $0.02 price point. However, documentation pages (`/docs`, `/pricing`, `/api`, `/README`) all returned only a "Connect wallet" prompt with no substantive content. There is no OpenAPI spec, no request/response schema documentation, and no examples available. The actual data or functionality behind this particular receipt endpoint is unclear — it could return a transaction receipt for a specific resource ID (122), but without documentation or sample responses this is speculative.

Capabilities

x402-paymentusdc-settlementbase-networkpay-per-callno-api-keytransaction-receiptjson-response

Use cases

  • —Retrieving transaction receipts via a pay-per-call model without needing API keys
  • —Agent-driven workflows that need on-demand access to transaction data with crypto micropayments
  • —Integrating low-cost USDC-settled API calls into Web3 applications

Fit

Best for

  • —Developers wanting keyless, pay-per-use API access settled in USDC on Base
  • —AI agents that can autonomously pay for API calls via x402 protocol
  • —Projects needing low-friction access without subscription commitments

Not for

  • —Users who need detailed API documentation or response schema before integrating
  • —High-volume use cases where per-request pricing may not be cost-effective compared to subscriptions
  • —Developers who cannot transact in USDC on the Base network

Quick start

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

Endpoint

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

Quality

0.35/ 1.00

The endpoint is live and returns a valid x402 402 challenge with clear pricing. However, there is no OpenAPI spec, no request/response schema, and all documentation pages are empty stubs showing only 'Connect wallet'. The purpose and output of this specific receipt endpoint are unclear.

Warnings

  • —No API documentation available — /docs, /pricing, /api, and /README all return only a 'Connect wallet' prompt with no content
  • —No OpenAPI or schema definition found for any endpoint
  • —No example request or response bodies available
  • —The specific functionality of /api/v1/transactions/122/receipt is undocumented and unclear — the hardcoded ID '122' suggests this may be a demo or placeholder resource

Citations

Provenance

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

Agent access

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