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

What it does

This endpoint at lowpaymentfee.com provides a transaction receipt resource (specifically for transaction ID 110) 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 utility services — all priced at $0.02 per request and settled in USDC on the Base network.

The specific endpoint `/api/v1/transactions/110/receipt` accepts POST requests and returns JSON. Payment is handled via the x402 protocol: callers must include an `X-PAYMENT` header with a valid payment proof. The x402 challenge advertises a maxAmountRequired of 20,000 base units of USDC (contract 0x8335…2913 on Base), which equals $0.02 given USDC's 6 decimals. The payment is sent to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 with a 300-second timeout.

The platform advertises no API keys, no rate limits, and instant access. Documentation pages (/docs, /pricing, /api, /README) all resolve but appear to require a wallet connection to view content, so detailed API schemas and response formats are not available from the crawl. The exact content returned by this receipt endpoint is unclear — the description simply says "Premium API Access" — so the actual payload structure must be discovered by making a paid request.

Capabilities

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

Use cases

  • —Retrieving a transaction receipt for transaction 110 via a micropayment
  • —Demonstrating x402 protocol integration for agent-to-agent payments
  • —Accessing premium data behind a crypto paywall without API key management

Fit

Best for

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

Not for

  • —Users who need detailed API documentation before purchasing
  • —High-volume batch retrieval where $0.02/request adds up quickly
  • —Anyone without a Base-compatible USDC wallet

Quick start

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

Endpoint

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

Quality

0.35/ 1.00

The endpoint is live (402 challenge confirmed) and pricing is clear ($0.02 USDC on Base). However, there is no OpenAPI schema, no response examples, and all documentation pages require wallet connection, yielding no usable content. The purpose of this specific receipt endpoint is vague — 'Premium API Access' is not descriptive. Effectively a stub listing.

Warnings

  • —Documentation pages (/docs, /pricing, /api, /README) all require wallet connection and returned no useful content during crawl.
  • —The exact response schema and payload of this receipt endpoint are unknown — 'Premium API Access' is the only description provided.
  • —This endpoint is for a specific transaction ID (110); it is unclear whether other transaction IDs are available or what the receipt contains.
  • —The broader platform lists many API categories (AI, analytics, finance, utilities) but none could be verified from crawl content.

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-19 11:50:56Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-18
Last seen2026-04-25

Agent access

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