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

What it does

This endpoint at lowpaymentfee.com provides access to a specific transaction receipt (transaction ID 381) 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 via the x402 protocol.

The specific endpoint probed (/api/v1/transactions/381/receipt) returns a valid x402 challenge with a maxAmountRequired of 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 made via the x402 "exact" scheme to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3. No API keys or rate limits are advertised; access is granted purely through per-request payment.

Documentation is extremely thin — the docs, API, pricing, and README pages all render only a "Connect wallet" prompt with no substantive content. There is no OpenAPI schema, no request/response examples, and no detailed documentation for any of the listed endpoints. The actual data returned by this receipt endpoint is unknown beyond the stated mimeType of application/json.

Capabilities

x402-paymentusdc-baseper-request-billingtransaction-receiptno-api-keypay-per-use

Use cases

  • —Retrieving a transaction receipt for transaction 381 via a single paid API call
  • —Demonstrating x402 protocol integration for per-request micropayments on Base
  • —Accessing paid API services without traditional API key registration

Fit

Best for

  • —Developers experimenting with x402 payment protocol integration
  • —Agents that need to make one-off paid API calls without account setup
  • —Low-volume, pay-as-you-go API consumption on Base

Not for

  • —Users needing detailed API documentation or OpenAPI specs before integrating
  • —High-volume batch retrieval where per-request pricing is inefficient
  • —Anyone without a Base-compatible USDC wallet

Quick start

# The endpoint requires an x402 payment header. First, obtain the 402 challenge:
curl -X POST https://lowpaymentfee.com/api/v1/transactions/381/receipt
# Returns 402 with x402 challenge. Construct X-PAYMENT header per x402 spec,
# paying 20000 base units ($0.02) USDC on Base to 0x1A2B...85F3, then retry:
curl -X POST -H "X-PAYMENT: <signed_payment>" https://lowpaymentfee.com/api/v1/transactions/381/receipt

Endpoint

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

Quality

0.30/ 1.00

The x402 challenge is live and pricing is clear ($0.02 USDC on Base), but there is no documentation, no OpenAPI schema, no request/response examples, and the docs pages are empty. The specific endpoint (transaction 381 receipt) is narrow and its output format is undocumented. This is effectively a stub listing.

Warnings

  • —No OpenAPI schema or endpoint documentation available — all doc pages render only 'Connect wallet'
  • —The specific endpoint is for a single transaction receipt (ID 381); unclear if this generalizes
  • —No request body schema or response schema documented
  • —No examples of successful responses available
  • —The broader platform lists many endpoints but none have been verified beyond this one

Citations

Provenance

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

Agent access

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