x402basequality 0.30

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

What it does

This endpoint at lowpaymentfee.com provides access to a transaction receipt resource (transaction ID 369) 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 price per call is $0.02 (20,000 base units of USDC with 6 decimals).

The broader lowpaymentfee.com platform advertises a suite of APIs spanning data analytics, AI/ML inference (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, the specific endpoint being listed here — `/api/v1/transactions/369/receipt` — is not among those advertised on the landing page, and its exact response payload is undocumented.

Documentation is extremely thin: the /docs, /pricing, /api, and /README pages all render only a "Connect wallet" prompt with no further content. There is no OpenAPI spec, no example request/response, and no detailed schema for what the receipt contains. The endpoint is confirmed live (returns a proper 402 challenge), but the lack of documentation makes it difficult to assess the actual utility of the returned data.

Capabilities

x402-paymentusdc-settlementbase-networktransaction-receiptjson-responseper-call-pricing

Use cases

  • —Retrieving a receipt for transaction 369 via programmatic x402 payment
  • —Demonstrating x402 pay-per-call integration on the Base network
  • —Agent-driven receipt fetching without API key management

Fit

Best for

  • —Developers experimenting with x402 payment protocol on Base
  • —Agents that need keyless, pay-per-call API access
  • —Testing USDC micropayment flows

Not for

  • —Production workloads requiring documented and stable API contracts
  • —Users needing bulk or batch transaction receipt retrieval
  • —Anyone who needs detailed schema documentation before integrating

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/transactions/369/receipt
# Returns 402 with x402 challenge; attach X-PAYMENT header with signed USDC payment to receive the receipt.

Endpoint

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

Quality

0.30/ 1.00

The endpoint is live and returns a valid x402 challenge, but there is no documentation, no OpenAPI spec, no example responses, and the specific resource (transaction 369 receipt) is not described anywhere on the site. The docs pages are empty beyond a wallet-connect prompt. This is effectively a stub listing.

Warnings

  • —No documentation available — /docs, /pricing, /api, and /README all show only 'Connect wallet'
  • —No OpenAPI or schema describing the receipt response payload
  • —The specific endpoint /api/v1/transactions/369/receipt is not listed among the site's advertised APIs
  • —Cannot verify what data the receipt actually contains

Citations

Provenance

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

Agent access

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