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

What it does

This endpoint at lowpaymentfee.com provides a transaction receipt resource (transaction ID 140) behind an x402 paywall. 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/140/receipt` accepts POST requests and returns `application/json`. Payment is handled via the x402 exact-payment scheme: the caller includes an X-PAYMENT header with a USDC payment of up to 20,000 base units (i.e., $0.02, since USDC uses 6 decimals) to the specified payTo address on Base. No API keys or rate limits are advertised; access is purely pay-per-call.

Documentation beyond the landing page is extremely thin — the /docs, /api, /pricing, and /README pages all render only a "Connect wallet" prompt with no additional technical detail. There is no OpenAPI spec, no request/response schema documentation, and no example payloads available. The endpoint is confirmed live (returns a proper 402 challenge), but the actual data returned after payment is unknown. The platform appears to be a demonstration or early-stage x402 service showcasing low-fee micropayments.

Capabilities

x402-paymentusdc-settlementbase-networktransaction-receiptpay-per-callno-api-keyjson-response

Use cases

  • —Retrieving a transaction receipt for transaction 140 via micropayment
  • —Demonstrating x402 protocol payment flows on Base
  • —Integrating pay-per-call APIs without API key management

Fit

Best for

  • —Developers experimenting with x402 payment protocol
  • —Agents that can settle USDC micropayments on Base
  • —Use cases requiring keyless, pay-as-you-go API access

Not for

  • —Production workloads requiring documented request/response schemas
  • —Users who need fiat-only payment options
  • —Bulk data retrieval at scale (no documented batch endpoints)

Quick start

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

Endpoint

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

Quality

0.30/ 1.00

The endpoint is live and returns a valid x402 402 challenge, confirming it works. However, there is no OpenAPI spec, no documented request body or response schema, and all secondary pages are empty wallet-connect stubs. The specific purpose of this particular 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, /api, /pricing, /README) render only 'Connect wallet' with no content.
  • —The specific endpoint is for a single transaction receipt (ID 140); unclear if this is a demo or production resource.
  • —Platform appears early-stage or demonstrative; reliability and uptime are unverified.

Citations

Provenance

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

Agent access

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