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

What it does

This endpoint at lowpaymentfee.com provides a transaction receipt resource (transaction ID 208) 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/208/receipt` accepts POST requests and returns `application/json`. Payment is handled via the x402 protocol: callers receive a 402 challenge containing the accepted payment scheme (exact), the USDC asset contract on Base (`0x8335…`), and a maximum amount of 20,000 base units (i.e., $0.02 given USDC's 6 decimals). No API keys or rate limits are advertised; access is granted purely through per-request micropayment.

The platform's landing page lists additional endpoints across analytics (metrics, reports, data export, insights), AI (sentiment analysis, text summarization, classification, embeddings), finance (price feeds, exchange rates, token quotes, gas estimates), and utilities (geocoding, validation, conversion, generation), all at the same $0.02 price point. However, no OpenAPI schema, detailed documentation, or example request/response payloads are available — the docs, API, pricing, and README pages all render only a "Connect wallet" prompt with no substantive content.

Capabilities

x402-paymentusdc-baseper-request-micropaymenttransaction-receiptjson-responsepost-method

Use cases

  • —Retrieving a transaction receipt for transaction 208 via a single micropayment
  • —Demonstrating x402 protocol integration for pay-per-call APIs
  • —Agent-driven programmatic access to receipts without API key management

Fit

Best for

  • —Developers experimenting with x402 pay-per-call patterns
  • —Agents that can settle USDC micropayments on Base
  • —Use cases requiring keyless, per-request API access

Not for

  • —Production workloads requiring documented request/response schemas
  • —Users who need bulk or subscription-based access at lower marginal cost
  • —Anyone without a Base-compatible USDC wallet

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/transactions/208/receipt
# Returns 402 with x402 challenge; attach X-PAYMENT header with signed USDC payment to access.

Endpoint

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

Quality

0.30/ 1.00

The endpoint is live and returns a valid x402 challenge with clear pricing, but there is no OpenAPI schema, no documentation beyond a wallet-connect prompt, no example request/response payloads, and the specific purpose of 'transaction 208 receipt' is unexplained. Effectively a stub listing.

Warnings

  • —No OpenAPI or schema documentation available — all doc pages render only 'Connect wallet'
  • —The specific resource (transaction 208 receipt) is unexplained; unclear what data it returns
  • —No example request or response bodies are available anywhere in the crawl
  • —The broader platform lists many endpoints but none have documented schemas or usage examples

Citations

Provenance

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

Agent access

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