x402basequality 0.35

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

What it does

This endpoint at lowpaymentfee.com provides a transaction receipt resource (transaction ID 312) behind an x402 paywall. It is part of a broader platform that offers a variety of pay-per-call APIs spanning data analytics, AI/ML inference, finance/Web3 data, and infrastructure utilities — all priced at $0.02 per request and settled in USDC on the Base network.

The specific endpoint `/api/v1/transactions/312/receipt` accepts POST requests and returns JSON. Payment is handled via the x402 protocol: callers receive a 402 challenge containing the payment parameters (asset, amount, payTo address) and must include a valid X-PAYMENT header to proceed. The max amount required is 20,000 base units of USDC (6 decimals), which equals $0.02. No API keys or rate limits are advertised; access is gated purely by micropayment.

The platform's landing page lists 16 endpoints across four categories (Data & Analytics, AI & Machine Learning, Finance & Web3, Infrastructure), all at the same $0.02 price point. However, documentation pages (/docs, /pricing, /api, /README) all render only a "Connect wallet" prompt with no substantive content, so there is no detailed schema documentation, request/response examples, or explanation of what data the receipt endpoint actually returns.

Capabilities

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

Use cases

  • —Retrieving a transaction receipt for transaction 312 via micropayment
  • —Demonstrating x402 protocol integration for pay-per-call APIs
  • —Agent-driven programmatic access to paid data without API key management

Fit

Best for

  • —Developers experimenting with x402 payment protocol
  • —Agents that can settle USDC micropayments on Base
  • —Use cases requiring keyless, pay-as-you-go API access

Not for

  • —Users needing detailed API documentation or schema guarantees before integrating
  • —High-volume batch retrieval where per-request fees add up
  • —Users without a Base-compatible USDC wallet

Quick start

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

Endpoint

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

Quality

0.35/ 1.00

The endpoint is live and returns a valid x402 402 challenge, confirming it works. However, all documentation pages are empty (just 'Connect wallet'), there is no OpenAPI spec, no request/response schema, and no explanation of what the receipt endpoint actually returns. The specific endpoint path (/transactions/312/receipt) appears to be a single hardcoded resource rather than a parameterized API. This is effectively a stub listing.

Warnings

  • —All documentation pages (/docs, /pricing, /api, /README) render only 'Connect wallet' with no actual content
  • —No OpenAPI or schema documentation available for any endpoint
  • —No request body schema or response schema documented — unclear what the receipt contains
  • —The endpoint path references a specific transaction ID (312); it is unclear whether this is parameterized or a single fixed resource
  • —The platform lists 16 endpoints across multiple domains but provides zero documentation for any of them

Citations

Provenance

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

Agent access

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