x402basequality 0.30

Transaction receipt endpoint on Base, paid per-call via x402 with USDC.

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

What it does

This endpoint at lowpaymentfee.com provides access to a transaction receipt (resource ID 348) behind an x402 paywall. The broader lowpaymentfee.com platform advertises a suite of API categories including Data & Analytics, AI & Machine Learning, Finance & Web3, and Infrastructure utilities — all priced at $0.02 per request, settled in USDC on the Base network with no API keys or rate limits required.

The specific endpoint `/api/v1/transactions/348/receipt` returns a 402 challenge requesting up to 20,000 base units of USDC (0x8335…2913 on Base), which equals $0.02 given USDC's 6 decimals. Payment is made via the x402 exact scheme by including an X-PAYMENT header. The response MIME type is application/json. The endpoint accepts POST requests and is marked as discoverable.

Documentation on the site is extremely thin — 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. The platform appears to be a demonstration or early-stage x402 API marketplace, but the actual data returned by this receipt endpoint is unspecified.

Capabilities

x402-paymentusdc-settlementbase-networktransaction-receiptper-call-pricingno-api-keyjson-response

Use cases

  • —Retrieving a transaction receipt for record ID 348 via micropayment
  • —Demonstrating x402 payment protocol integration on Base
  • —Agent-driven pay-per-call data retrieval without API key management

Fit

Best for

  • —Developers experimenting with x402 protocol payments
  • —Agents needing keyless, pay-per-call API access on Base
  • —Projects requiring USDC-settled micropayment endpoints

Not for

  • —Production workloads requiring documented request/response schemas
  • —Bulk data retrieval where per-call pricing is inefficient
  • —Users who need fiat payment rails or non-crypto settlement

Quick start

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

Endpoint

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

Quality

0.30/ 1.00

The endpoint is live (402 challenge confirmed) and pricing is clear ($0.02 USDC on Base), but there is no documentation, no OpenAPI spec, no request/response schema, and no examples. The /docs and other pages render only a wallet-connect prompt. The specific purpose of the 'transactions/348/receipt' resource is unexplained.

Warnings

  • —No OpenAPI spec or schema documentation available
  • —All documentation pages (/docs, /pricing, /api, /README) render only 'Connect wallet' with no content
  • —The specific data returned by this receipt endpoint is completely undocumented
  • —Purpose of resource ID 348 is unclear — may be a demo or placeholder
  • —Platform appears to be early-stage or a proof-of-concept

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-19 13:21:28Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-18
Last seen2026-07-23

Agent access

JSONhttps://clawmart.sh/api/listings/cwx8Vq
Transaction receipt endpoint on Base, paid per-call via x402 with USDC. — Clawmart · Clawmart