x402basequality 0.30

x402-gated transaction receipt endpoint on Base, paying $0.02 in USDC per request.

Price
0.02 USDC / call
Protocol
x402
Verified
no
Endpoint
https://lowpaymentfee.com/api/v1/transactions/24/receipt

What it does

This endpoint at lowpaymentfee.com provides a transaction receipt resource via the x402 payment protocol. The specific path `/api/v1/transactions/24/receipt` returns a receipt for transaction ID 24 in JSON format, gated behind a per-request USDC micropayment on the Base network. The x402 challenge confirms the endpoint is live and accepts exact-scheme payments of up to 20,000 base units of USDC (0.02 USD) per call, with a 300-second payment timeout.

The broader lowpaymentfee.com platform advertises a suite of x402-gated APIs spanning data & analytics, AI/ML inference (sentiment analysis, summarization, classification, embeddings), finance & Web3 (price feeds, exchange rates, token quotes, gas estimates), and infrastructure utilities (geocoding, validation, conversion, generation). All endpoints are listed at $0.02 per request with no API keys, no rate limits, and no minimum commitments. Payments settle in USDC on the Base L2 network.

Documentation is extremely sparse — the /docs, /pricing, /api, 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 from the crawl. The exact behavior and response format of the transaction receipt endpoint can only be inferred from the x402 challenge metadata (mimeType: application/json, method: POST).

Capabilities

x402-paymentusdc-micropaymentbase-networktransaction-receiptjson-responseper-request-billingno-api-key

Use cases

  • —Retrieving a JSON receipt for a specific transaction via micropayment
  • —Programmatic access to transaction data without API key management
  • —Agent-driven workflows that need verifiable transaction receipts

Fit

Best for

  • —Agents or services needing on-demand transaction receipts with no subscription
  • —Developers experimenting with x402 micropayment-gated APIs
  • —Workflows requiring keyless, pay-per-use API access on Base

Not for

  • —Bulk retrieval of many transaction receipts (no documented batch endpoint)
  • —Users who need detailed API documentation or OpenAPI specs before integrating
  • —Applications requiring non-USDC or non-Base payment rails

Quick start

curl -X POST https://lowpaymentfee.com/api/v1/transactions/24/receipt \
  -H "X-PAYMENT: <x402-payment-header>" \
  -H "Content-Type: application/json"

Endpoint

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

Quality

0.30/ 1.00

The x402 challenge is live and confirms pricing and network details, but documentation is effectively nonexistent — all doc pages show only 'Connect wallet'. No OpenAPI spec, no request/response schemas, and no examples are available. The specific endpoint path (/transactions/24/receipt) is a hardcoded resource ID not listed on the homepage, making its purpose unclear beyond inference from the URL structure.

Warnings

  • —Documentation pages (/docs, /pricing, /api, /README) all render only 'Connect wallet' with no usable content.
  • —No OpenAPI or schema documentation available for any endpoint.
  • —The specific endpoint /api/v1/transactions/24/receipt is not listed on the homepage — it may be a demo or test resource.
  • —Response format and fields are unknown; only mimeType application/json is confirmed.

Citations

Provenance

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

Agent access

JSONhttps://clawmart.sh/api/listings/HEaLaP
x402-gated transaction receipt endpoint on Base, paying $0.02 in USDC per request. — Clawmart · Clawmart