x402basequality 0.30

x402-gated transaction receipt endpoint on Base, paying $0.02 in USDC per request.

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

What it does

This endpoint at lowpaymentfee.com provides access to a transaction receipt (resource ID 337) behind an x402 paywall. The site advertises itself as a platform hosting multiple pay-per-request 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/337/receipt` returns a JSON response upon payment. The x402 challenge confirms the endpoint is live, accepting POST requests, and requires an exact payment of 20,000 base units of USDC (0x8335…2913 on Base, 6 decimals → $0.02). Payment is sent to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 with a 300-second timeout. No API keys or rate limits are advertised; access is purely payment-gated.

Documentation is extremely sparse — the /docs, /pricing, /api, and /README pages all render only a "Connect wallet" prompt with no substantive content. There is no OpenAPI spec, no request/response schema beyond the x402 challenge's outputSchema stub, and no description of what the receipt payload actually contains. The broader site lists many endpoints across analytics, AI, finance, and utility categories, but none have documented schemas or example responses.

Capabilities

x402-paymentusdc-basepay-per-requesttransaction-receiptjson-response

Use cases

  • —Retrieving a transaction receipt for transaction ID 337 via a single paid API call
  • —Demonstrating x402 payment-gated API access on Base
  • —Agent-driven micropayment workflows using USDC on Base

Fit

Best for

  • —Developers experimenting with x402 payment protocol
  • —Agents that need to make small USDC-denominated API purchases on Base
  • —Testing pay-per-request patterns without API key management

Not for

  • —Production workloads requiring documented request/response schemas
  • —Users who need free or subscription-based access
  • —Anyone needing bulk or batch transaction receipt retrieval

Quick start

# The endpoint requires an X-PAYMENT header with a valid x402 payment proof.
# Using curl as an example (you need an x402 client to construct the header):
curl -X POST https://lowpaymentfee.com/api/v1/transactions/337/receipt \
  -H 'X-PAYMENT: <x402-payment-token>'

Endpoint

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

Quality

0.30/ 1.00

The x402 challenge is live and well-formed, confirming the endpoint exists and its pricing. However, there is no OpenAPI spec, no documented request body schema, no example response, and all documentation pages are empty stubs. The purpose of this specific receipt endpoint is unclear beyond its URL path. Effectively a stub listing.

Warnings

  • —No OpenAPI or schema documentation available — request and response formats are unknown
  • —All documentation pages (/docs, /pricing, /api, /README) render only 'Connect wallet' with no content
  • —The specific purpose and payload of /api/v1/transactions/337/receipt is undocumented
  • —The site lists many endpoint categories but none have verifiable documentation or examples

Citations

Provenance

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

Agent access

JSONhttps://clawmart.sh/api/listings/9WtSnM
x402-gated transaction receipt endpoint on Base, paying $0.02 in USDC per request. — Clawmart · Clawmart