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

What it does

This endpoint at lowpaymentfee.com provides a transaction receipt resource (transaction ID 67) 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/67/receipt` accepts POST requests and returns `application/json`. Payment is handled via the x402 protocol: callers receive a 402 challenge specifying the USDC asset contract on Base (`0x8335…2913`), and must attach an `X-PAYMENT` header with a signed payment of up to 20,000 base units (i.e., $0.02 USDC, since USDC uses 6 decimals). No API keys or rate limits are advertised; access is purely pay-per-call.

The platform's documentation, pricing, and API reference pages all appear to require a wallet connection and contain no additional rendered content. There is no OpenAPI spec, no detailed schema documentation, and no example request/response payloads available from the crawl. The exact data returned by this receipt endpoint is unknown beyond the stated MIME type of `application/json`. The broader site lists many endpoints across several domains but provides no further technical detail about any of them.

Capabilities

x402-paymentusdc-settlementbase-networkper-call-pricingtransaction-receiptjson-response

Use cases

  • —Retrieving a transaction receipt for transaction 67 via a micropayment-gated API call
  • —Demonstrating x402 protocol integration for agent-to-agent commerce
  • —Testing USDC micropayment flows on Base network

Fit

Best for

  • —Developers experimenting with x402 payment protocol
  • —Agents that need to fetch transaction receipts with no API key setup
  • —Low-friction pay-per-call access without subscriptions

Not for

  • —Production workloads requiring documented schemas and SLAs
  • —Bulk retrieval of many different transaction receipts (endpoint is scoped to transaction 67)
  • —Users who need fiat-only payment rails

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/transactions/67/receipt
# Returns 402 with x402 challenge. Attach X-PAYMENT header with signed USDC payment on Base to complete.

Endpoint

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

Quality

0.30/ 1.00

The endpoint is live (402 challenge captured) and pricing is clear ($0.02 USDC on Base), but there is no OpenAPI spec, no documentation beyond a landing page, no example request/response, and the endpoint is scoped to a single hardcoded transaction ID (67). The docs/pricing/API pages all render only a wallet-connect prompt with no useful content.

Warnings

  • —No OpenAPI or schema documentation available — response format is unknown beyond application/json
  • —Endpoint is scoped to a single transaction ID (67); unclear if this is a demo or production resource
  • —All documentation pages (docs, api, pricing, README) render only a wallet-connect prompt with no content
  • —The broader platform lists many endpoints but provides zero technical detail for any of them
  • —No robots.txt or agents.txt present

Citations

Provenance

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

Agent access

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