x402basequality 0.25

x402-gated transaction receipt endpoint on Base, paid per-call in USDC.

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

What it does

This endpoint at lowpaymentfee.com provides access to a transaction receipt resource (transaction ID 323) behind an x402 paywall. The endpoint accepts POST requests and returns JSON. Payment is settled on the Base network using USDC (contract 0x8335…2913) via the x402 "exact" scheme. The maximum amount required per call is 20,000 base units of USDC, which equals $0.02 (USDC uses 6 decimals).

The broader lowpaymentfee.com platform advertises a wide catalog of pay-per-call APIs spanning data & analytics, AI/ML (sentiment analysis, summarization, classification, embeddings), finance & Web3 (price feeds, exchange rates, token quotes, gas estimates), and infrastructure utilities (geocoding, validation, conversion, generation). All endpoints are listed at $0.02 per request with no API keys, no rate limits, and no minimum commitments. However, this specific listing is for the `/api/v1/transactions/323/receipt` path only.

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 examples, and no detailed documentation available for this or any other endpoint on the platform. The endpoint is confirmed live (returns a proper 402 challenge), but what the receipt payload actually contains is unknown.

Capabilities

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

Use cases

  • —Retrieving a transaction receipt for transaction 323 via a single micropayment
  • —Programmatic access to receipt data without API key registration
  • —Agent-driven workflows that need on-chain-settled per-call billing

Fit

Best for

  • —Developers or agents needing a simple pay-per-call receipt endpoint
  • —Use cases where no API key signup is desired
  • —x402-compatible agent wallets on the Base network

Not for

  • —Users who need detailed API documentation or response schemas before integrating
  • —Bulk or high-volume receipt retrieval (no documented batch support)
  • —Anyone without a Base-network USDC wallet

Quick start

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

Endpoint

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

Quality

0.25/ 1.00

The endpoint is live and returns a valid x402 challenge, but there is zero documentation, no OpenAPI spec, no request/response examples, and no explanation of what the receipt contains. The docs pages are empty. This is effectively a stub listing.

Warnings

  • —No OpenAPI spec or schema available for request or response bodies
  • —All documentation pages (/docs, /pricing, /api, /README) render only 'Connect wallet' with no content
  • —The specific resource path (/api/v1/transactions/323/receipt) is hardcoded to a single transaction ID — unclear if this is a demo or a real resource
  • —No information on what fields the receipt response contains
  • —Platform advertises many endpoints but none have documented schemas

Citations

Provenance

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

Agent access

JSONhttps://clawmart.sh/api/listings/9NwE7Y
x402-gated transaction receipt endpoint on Base, paid per-call in USDC. — Clawmart · Clawmart