x402basequality 0.40

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

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

What it does

This endpoint at lowpaymentfee.com provides a transaction receipt retrieval service accessible via the x402 payment protocol. It is part of a broader platform offering multiple API categories including Data & Analytics, AI & Machine Learning, Finance & Web3, and Infrastructure utilities—all priced at $0.02 per request settled in USDC on the Base network.

The specific endpoint `/api/v1/transactions/373/receipt` returns a JSON receipt for transaction ID 373. Payment is handled inline: callers send an X-PAYMENT header containing a signed USDC payment of up to 20,000 base units ($0.02, since USDC uses 6 decimals) to the specified payTo address on Base. No API keys, rate limits, or subscriptions are required—access is purely pay-per-use.

The platform advertises instant access with no minimums or commitments. Documentation pages exist but appear gated behind a wallet connection, so detailed request/response schemas are not publicly documented. The x402 challenge confirms the endpoint is live, accepts POST requests, and returns application/json content.

Capabilities

x402-paymentusdc-settlementbase-networktransaction-receiptpay-per-callno-api-keyjson-response

Use cases

  • —Retrieving transaction receipts programmatically with per-call payment
  • —Integrating pay-per-use APIs without subscription overhead
  • —Agent-driven workflows that need verifiable transaction data on demand

Fit

Best for

  • —Developers wanting zero-commitment API access paid in USDC
  • —AI agents that need to fetch transaction receipts autonomously
  • —Projects already operating on the Base L2 network

Not for

  • —High-volume batch processing where per-call pricing is inefficient
  • —Users without USDC on Base network
  • —Applications requiring detailed API documentation before integration

Quick start

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

Endpoint

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

Quality

0.40/ 1.00

The endpoint is confirmed live via a valid 402 challenge with clear pricing and network details. However, no OpenAPI schema, no request/response examples, and documentation pages are gated behind wallet connection, leaving the actual response format unknown.

Warnings

  • —Documentation pages are gated behind wallet connection—no public schema or examples available
  • —The specific endpoint path includes a hardcoded transaction ID (373), suggesting it may be a single-resource endpoint rather than a general-purpose API
  • —No response schema or example output is documented anywhere in the crawl

Citations

Provenance

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

Agent access

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