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

What it does

This endpoint at lowpaymentfee.com provides a transaction receipt resource (transaction ID 136) 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/136/receipt` accepts POST requests and returns `application/json`. Payment is handled via the x402 exact-payment scheme: the caller must attach an X-PAYMENT header containing a signed 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 gated entirely by the per-request micropayment.

While the platform homepage lists many endpoints across analytics, AI, finance, and utility categories, the crawled documentation pages (`/docs`, `/api`, `/pricing`, `/README`) all returned only a "Connect wallet" prompt with no substantive content. There is no OpenAPI spec, no request/response schema documentation, and no examples available. The actual behavior and data returned by this specific receipt endpoint — or any of the other listed endpoints — cannot be verified from the available material.

Capabilities

x402-paymentusdc-micropaymentbase-networktransaction-receiptjson-responseper-call-billing

Use cases

  • —Retrieving a transaction receipt for transaction 136 via a single micropayment
  • —Demonstrating x402 pay-per-request integration on Base
  • —Agent-driven programmatic access to paid receipt data without API keys

Fit

Best for

  • —Developers experimenting with x402 payment protocol on Base
  • —Agents that can sign USDC payments for per-call API access
  • —Use cases requiring keyless, pay-as-you-go API consumption

Not for

  • —Users needing detailed API documentation or request/response schemas before integrating
  • —High-volume batch retrieval where per-call micropayments add up
  • —Anyone without a Base-compatible wallet holding USDC

Quick start

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

Endpoint

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

Quality

0.30/ 1.00

The endpoint is live (returns a valid x402 402 challenge), but there is no OpenAPI spec, no documented request/response schema, no examples, and the docs/pricing/README pages are all empty beyond a wallet-connect prompt. The specific purpose of this receipt endpoint is unclear beyond its URL path. Effectively a stub listing.

Warnings

  • —No OpenAPI or schema documentation available for any endpoint on this platform
  • —All documentation pages (/docs, /api, /pricing, /README) returned only 'Connect wallet' with no content
  • —The specific data returned by this receipt endpoint is unknown — no response schema or example exists
  • —The platform lists many endpoint categories (AI, analytics, finance, utilities) but none have verifiable documentation
  • —Cannot confirm what data or functionality any of the advertised endpoints actually provide

Citations

Provenance

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

Agent access

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