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

What it does

This endpoint at lowpaymentfee.com provides a transaction receipt resource (transaction ID 92) behind an x402 paywall. The broader lowpaymentfee.com platform advertises a suite of pay-per-request APIs spanning data analytics, AI/ML inference (sentiment analysis, summarization, classification, embeddings), finance/Web3 data (price feeds, exchange rates, token quotes, gas estimates), and infrastructure utilities (geocoding, validation, conversion, generation). All endpoints are priced at $0.02 per request, settled in USDC on the Base network, with no API keys, no rate limits, and no minimum commitments.

The specific endpoint probed — `/api/v1/transactions/92/receipt` — returns a valid x402 challenge (version 1, scheme "exact") requesting up to 20,000 base units of USDC (0x8335…2913 on Base). Since USDC uses 6 decimals, this translates to $0.02 per call, consistent with the site's advertised pricing. Payment is sent to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 with a 300-second timeout. The endpoint accepts POST requests and returns application/json.

Documentation is extremely thin — 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 documentation, and no example payloads available. The actual data returned by this receipt endpoint after payment is unknown from the crawled material.

Capabilities

x402-paymentusdc-settlementbase-networkper-request-pricingtransaction-receiptjson-responsepost-method

Use cases

  • —Retrieving transaction receipts via micropayment-gated API calls
  • —Programmatic access to paid data endpoints without API key management
  • —Agent-driven workflows that need on-demand paid resource access on Base

Fit

Best for

  • —Developers experimenting with x402 payment protocol integrations
  • —Agents that can settle USDC payments on Base for per-call API access
  • —Use cases requiring no-signup, no-API-key access to paid endpoints

Not for

  • —Users who need detailed API documentation or OpenAPI specs before integrating
  • —High-volume consumers who need bulk pricing or subscription plans
  • —Anyone without a Base-compatible USDC wallet

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/transactions/92/receipt
# Returns 402 with x402 challenge; include X-PAYMENT header with signed USDC payment to complete request.

Endpoint

URLhttps://lowpaymentfee.com/api/v1/transactions/92/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 ($0.02 USDC on Base). However, there is no documentation, no OpenAPI spec, no request/response schema, and no examples. The docs pages are empty stubs. The specific purpose of this 'transaction 92 receipt' endpoint is unclear.

Warnings

  • —No API documentation available — docs, pricing, and README pages all show only 'Connect wallet' with no content
  • —No OpenAPI or schema definition; request body and response structure are completely unknown
  • —The specific endpoint path (/api/v1/transactions/92/receipt) appears to be a single hardcoded transaction ID rather than a parameterized resource
  • —The broader platform advertises many endpoints but none have documented schemas or examples

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-19 13:47:42Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-18
Last seen2026-04-23

Agent access

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