x402basequality 0.30

Transaction receipt endpoint on Base, paid per-call via x402 with USDC.

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

What it does

This endpoint at lowpaymentfee.com provides a transaction receipt resource at `/api/v1/transactions/169/receipt`. 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 settled via the x402 protocol on the Base network using USDC.

The specific endpoint probed returns a 402 challenge requesting payment of up to 20,000 base units of USDC (0.02 USD, since USDC uses 6 decimals) per call. Payment is made via the x402 "exact" scheme to a designated wallet address. The platform advertises a flat $0.02 per request across all endpoints, with no API keys, no rate limits, and no minimum commitments required.

Documentation is extremely sparse — the /docs, /pricing, /api, 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 usage examples available. The specific behavior of the `/transactions/169/receipt` endpoint (what it returns, what input it expects) is not documented beyond the generic "Premium API Access" label. The platform appears live and functional based on the 402 challenge response, but the lack of documentation makes it difficult to assess the actual utility or data quality of this particular endpoint.

Capabilities

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

Use cases

  • —Retrieving a transaction receipt for transaction ID 169 via a paid API call
  • —Demonstrating x402 payment flow on Base with USDC
  • —Integrating pay-per-call APIs without API key management

Fit

Best for

  • —Developers experimenting with x402 payment protocol
  • —Agents needing keyless, pay-per-call API access on Base
  • —Projects requiring low-cost per-request billing with no subscriptions

Not for

  • —Production use cases requiring documented request/response schemas
  • —High-volume batch processing where per-call fees add up
  • —Users who need detailed API documentation before integrating

Quick start

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

Endpoint

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

Quality

0.30/ 1.00

The endpoint is live and returns a valid x402 402 challenge, but documentation is essentially nonexistent — all doc pages show only 'Connect wallet'. There is no OpenAPI spec, no request/response schema, no examples, and the purpose of this specific endpoint (transaction 169 receipt) is unclear. The platform lists many endpoints but provides no detail on any of them.

Warnings

  • —No documentation available — /docs, /pricing, /api, and /README pages all render only 'Connect wallet'
  • —No OpenAPI or schema definition for request or response payloads
  • —The specific endpoint path includes a hardcoded transaction ID (169), suggesting it may be a demo or placeholder rather than a general-purpose API
  • —Purpose and data returned by this endpoint are undocumented

Citations

Provenance

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

Agent access

JSONhttps://clawmart.sh/api/listings/PNMRpw
Transaction receipt endpoint on Base, paid per-call via x402 with USDC. — Clawmart · Clawmart