x402basequality 0.30

Pay-per-call transaction receipt endpoint on Base via x402, settling in USDC at $0.02/request.

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

What it does

This x402-enabled endpoint at lowpaymentfee.com provides a "Premium API Access" transaction receipt resource. When called via POST, it returns a JSON receipt for transaction ID 68. Payment is settled on the Base network using USDC (contract 0x8335…2913) through the x402 exact payment scheme.

The endpoint charges a maximum of 20,000 base units of USDC (6 decimals), which equals $0.02 per request. The provider's landing page confirms a flat $0.02/request pricing model across all their endpoints, with no API keys, no rate limits, and instant access. The broader lowpaymentfee.com platform advertises additional API categories including Data & Analytics (metrics, reports, data export, insights), AI & Machine Learning (sentiment analysis, text summarization, classification, embeddings), Finance & Web3 (price feeds, exchange rates, token quotes, gas estimates), and Infrastructure utilities (geocoding, validation, conversion, generation) — all at the same $0.02 price point.

Documentation is extremely sparse. The /docs, /api, /pricing, and /README pages all render only a "Connect wallet" prompt with no substantive content. There is no OpenAPI spec, no request/response schema documentation, and no examples of what the receipt payload actually contains. The endpoint is confirmed live (returns a proper 402 x402 challenge), but the lack of documentation makes it difficult to know what data the receipt contains or what input the POST body expects.

Capabilities

x402-paymentusdc-settlementbase-networktransaction-receiptpay-per-callno-api-key

Use cases

  • —Retrieving a transaction receipt for transaction 68 via a single paid API call
  • —Demonstrating x402 pay-per-call patterns on the Base network
  • —Agent-driven micropayment workflows settling in USDC

Fit

Best for

  • —Developers experimenting with x402 payment protocols
  • —Agents needing pay-per-call access without API key management
  • —Low-cost USDC-settled API consumption on Base

Not for

  • —Production workloads requiring documented request/response schemas
  • —Bulk or high-volume receipt retrieval (no batch endpoint documented)
  • —Users who need fiat-only payment rails

Quick start

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

Endpoint

URLhttps://lowpaymentfee.com/api/v1/transactions/68/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, but there is no OpenAPI spec, no request/response schema, no documentation beyond a wallet-connect prompt, and the specific endpoint path (/transactions/68/receipt) suggests a single hardcoded resource rather than a general-purpose API. Effectively a stub listing.

Warnings

  • —No OpenAPI or schema documentation available — request body and response format are unknown
  • —All documentation pages (/docs, /api, /pricing, /README) render only 'Connect wallet' with no content
  • —The endpoint path references a specific transaction ID (68), suggesting it may not be a general-purpose resource
  • —The broader platform advertises many API categories (AI, finance, analytics, infrastructure) but none have documented schemas

Citations

Provenance

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

Agent access

JSONhttps://clawmart.sh/api/listings/pVSmuw
Pay-per-call transaction receipt endpoint on Base via x402, settling in USDC at $0.02/request. — Clawmart · Clawmart