x402basequality 0.25

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

What it does

This endpoint at lowpaymentfee.com provides a transaction receipt via the x402 payment protocol. It is part of a broader platform that advertises multiple API categories — data & analytics, AI & machine learning, finance & Web3, and infrastructure utilities — all gated behind x402 micropayments at $0.02 per request settled in USDC on the Base network.

The specific endpoint `/api/v1/transactions/2/receipt` accepts POST requests and returns a JSON response. The x402 challenge confirms the endpoint is live, requesting a maximum of 20,000 base units of USDC (0.02 USD, since USDC uses 6 decimals) paid to address `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3` using the "exact" payment scheme. The asset contract `0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913` is the canonical USDC contract on Base. No API keys or rate limits are advertised; access is purely pay-per-call.

Documentation is extremely sparse. The docs, API, pricing, and README pages all render only a "Connect wallet" prompt with no substantive content. There is no OpenAPI schema, no request/response examples, and no description of what the receipt endpoint actually returns or what parameters it accepts. The platform's landing page lists many endpoints across several domains, but without documentation it is unclear how functional or complete these services are.

Capabilities

x402-paymentusdc-micropaymentbase-networktransaction-receiptpay-per-requestno-api-key

Use cases

  • —Retrieving a transaction receipt via a single micropayment
  • —Demonstrating x402 protocol integration for pay-per-call APIs
  • —Programmatic access to receipt data without API key management

Fit

Best for

  • —Developers experimenting with x402 payment protocol
  • —Agents that need keyless, pay-per-call API access on Base
  • —Low-volume, on-demand transaction receipt retrieval

Not for

  • —Production workloads 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/2/receipt
# Returns 402 with x402 challenge; attach X-PAYMENT header with USDC payment proof on Base to access.

Endpoint

URLhttps://lowpaymentfee.com/api/v1/transactions/2/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 no documentation, no OpenAPI schema, no request/response examples, and the docs pages are empty. The purpose of the 'transactions/2/receipt' endpoint is unclear beyond its name. This is effectively a stub listing.

Warnings

  • —No API documentation available — docs, pricing, API, and README pages all show only 'Connect wallet'
  • —No OpenAPI or schema describing request parameters or response format
  • —Purpose and content of the receipt endpoint are not documented
  • —The platform lists many endpoints but none have visible documentation; functional completeness is unknown

Citations

Provenance

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

Agent access

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