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

What it does

This endpoint at lowpaymentfee.com provides access to a transaction receipt (resource ID 392) behind an x402 payment wall. The endpoint accepts POST requests and returns JSON. Payment is settled on the Base network using USDC (contract 0x8335…2913) via the x402 "exact" scheme. The maximum amount required per call is 20,000 base units of USDC, which equals $0.02 (USDC uses 6 decimals).

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 and crypto market data, 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. However, this specific listing is for the `/api/v1/transactions/392/receipt` path, which appears to be a transaction receipt retrieval endpoint rather than one of the advertised category APIs.

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 from the crawl. The endpoint is confirmed live (returns a proper 402 x402 challenge), but the actual response payload structure is unknown.

Capabilities

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

Use cases

  • —Retrieving a transaction receipt for transaction ID 392 via programmatic payment
  • —Demonstrating x402 protocol payment flows on the Base network
  • —Agent-driven micropayment API consumption without API key management

Fit

Best for

  • —Developers experimenting with x402 payment protocol integrations
  • —Agents that need to fetch transaction receipts with per-call crypto payments
  • —Use cases requiring keyless, pay-as-you-go API access on Base

Not for

  • —Users needing detailed API documentation or response schema guarantees
  • —High-volume batch retrieval where per-call pricing is inefficient
  • —Anyone without a Base-network USDC wallet

Quick start

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

Endpoint

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

Quality

0.30/ 1.00

The endpoint is confirmed live via a valid 402 x402 challenge, and pricing is clear ($0.02 USDC on Base). However, there is no OpenAPI spec, no documentation beyond a wallet-connect prompt, no request/response schema, and no examples. The specific resource (transaction 392 receipt) is opaque with no explanation of what it returns. This is effectively a stub listing.

Warnings

  • —No API documentation available — /docs, /api, /pricing, and /README all show only 'Connect wallet'
  • —No OpenAPI or schema definition found for request or response payloads
  • —The endpoint path references a specific transaction ID (392); unclear if this is a demo or a fixed resource
  • —The broader platform advertises many API categories but none have documented schemas or examples
  • —Cannot verify what data the receipt endpoint actually returns without making a paid request

Citations

Provenance

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

Agent access

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