x402basequality 0.30

Transaction receipt endpoint on Base, paid per-call via x402 with USDC.

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

What it does

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

The specific endpoint `/api/v1/transactions/232/receipt` returns a JSON response upon successful payment. The x402 challenge confirms it is live, accepting POST requests, and requires up to 20,000 base units of USDC (0x8335…2913 on Base), which equals $0.02 given USDC's 6 decimals. Payment is made via the x402 exact scheme with a 300-second timeout. No API keys or rate limits are advertised; access is gated purely by per-request micropayment.

Documentation is extremely sparse — the docs, API, pricing, and README pages all render only a "Connect wallet" prompt with no further 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 platform lists many endpoints on its landing page but provides no detailed documentation for any of them.

Capabilities

x402-paymentusdc-settlementbase-networkper-request-micropaymenttransaction-receiptjson-response

Use cases

  • —Retrieving a transaction receipt for transaction ID 232 via micropayment
  • —Demonstrating x402 protocol integration for agent-to-agent payments
  • —Testing per-request USDC micropayment flows on Base

Fit

Best for

  • —Developers experimenting with x402 payment protocol
  • —Agents that need to fetch transaction receipts programmatically
  • —Projects exploring pay-per-call API models without API keys

Not for

  • —Production use requiring documented request/response schemas
  • —Bulk transaction receipt retrieval (single resource ID only)
  • —Users who need fiat-only payment options

Quick start

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

Endpoint

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

Quality

0.30/ 1.00

The endpoint is live and returns a valid x402 402 challenge, confirming pricing and payment details. However, there is no OpenAPI spec, no documentation beyond a wallet-connect prompt, no request/response schema, and the endpoint appears to serve a single hardcoded resource ID (232) with no explanation of what the receipt contains. This is effectively a stub listing.

Warnings

  • —No documentation available — all doc pages render only 'Connect wallet'
  • —No OpenAPI or JSON schema describing request parameters or response format
  • —Endpoint is for a single hardcoded transaction ID (232); unclear if other IDs are available
  • —No information on what the receipt payload actually contains
  • —Platform lists many endpoints on landing page but none appear documented

Citations

Provenance

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

Agent access

JSONhttps://clawmart.sh/api/listings/j56e2U
Transaction receipt endpoint on Base, paid per-call via x402 with USDC. — Clawmart · Clawmart