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

What it does

This endpoint at lowpaymentfee.com provides access to a specific transaction receipt (transaction ID 278) 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 required.

The specific endpoint probed (/api/v1/transactions/278/receipt) returned a valid x402 challenge with a maxAmountRequired of 20,000 base units of USDC (0x8335… 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 the specified payTo address. The endpoint accepts POST requests and returns application/json.

Documentation is extremely sparse: the /docs, /api, /pricing, and /README pages all render only a "Connect wallet" prompt with no further technical detail. There is no OpenAPI spec, no request/response schema documentation, and no usage examples available. The exact structure of the receipt response and what request body (if any) is expected are unknown.

Capabilities

x402-paymentusdc-settlementbase-networktransaction-receiptpay-per-requestno-api-keyjson-response

Use cases

  • —Retrieving a transaction receipt for transaction 278 via a single micropayment
  • —Programmatic access to paid API endpoints without traditional API key management
  • —Agent-driven workflows that settle per-call costs in USDC on Base

Fit

Best for

  • —Developers or agents wanting keyless, pay-per-use API access
  • —Use cases requiring on-chain USDC micropayments on Base
  • —Scenarios where no subscription or rate-limit management is desired

Not for

  • —Users needing detailed API documentation or request/response schemas before integrating
  • —High-volume batch processing where per-call pricing may add up
  • —Users who cannot transact in USDC on the Base network

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/transactions/278/receipt
# Returns 402 with x402 challenge; attach X-PAYMENT header with valid USDC payment proof to receive the receipt.

Endpoint

URLhttps://lowpaymentfee.com/api/v1/transactions/278/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. However, documentation is essentially nonexistent — all doc pages show only 'Connect wallet'. There is no OpenAPI spec, no request/response schema, no examples, and the purpose of this specific receipt endpoint is unclear beyond its URL path. The broader platform lists many endpoints but provides no technical details for any of them.

Warnings

  • —No API documentation available — /docs, /api, /pricing, and /README pages all render only 'Connect wallet'
  • —No OpenAPI or schema definition found for any endpoint on the platform
  • —The specific endpoint is for a single transaction receipt (ID 278); unclear if this is a demo or a production resource
  • —Request body format and response schema are completely undocumented

Citations

Provenance

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

Agent access

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