x402basequality 0.30

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

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

What it does

This x402-enabled endpoint at lowpaymentfee.com provides access to a transaction receipt resource at `/api/v1/transactions/252/receipt`. It is part of a broader platform offering multiple API categories — data & analytics, AI & machine learning, finance & Web3, and infrastructure utilities — all gated behind x402 micropayments on the Base network using USDC.

The specific endpoint probed returns a 402 challenge requesting payment of up to 20,000 base units of USDC (0x8335…2913 on Base, 6 decimals), which equals $0.02 per request. Payment is made via the x402 exact scheme to the specified payTo address. The platform advertises a uniform $0.02/request pricing across all endpoints, with no API keys, no rate limits, and no minimum commitments required.

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 schema, no request/response examples, and no detailed description of what the transaction receipt endpoint actually returns. The endpoint accepts POST requests and returns application/json, but the exact payload structure is unknown. The platform appears to be a demonstration or early-stage x402 API marketplace.

Capabilities

x402-paymentusdc-basepay-per-calltransaction-receiptjson-responseno-api-keymicropayment

Use cases

  • —Retrieving transaction receipt data via a single micropayment
  • —Testing x402 payment flows on the Base network
  • —Integrating pay-per-call APIs without API key management

Fit

Best for

  • —Developers experimenting with x402 protocol payments
  • —Agents that need keyless, pay-per-call API access on Base
  • —Low-volume consumers who want no subscription commitments

Not for

  • —Production workloads requiring documented request/response schemas
  • —Users needing bulk or high-throughput data retrieval with predictable SLAs
  • —Anyone without a Base-compatible USDC wallet

Quick start

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

Endpoint

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

Quality

0.30/ 1.00

The endpoint is live and returns a valid x402 402 challenge, confirming pricing and payment details. However, documentation is essentially nonexistent — all doc pages show only 'Connect wallet'. There is no OpenAPI schema, no request/response examples, and no description of what the receipt endpoint actually returns. The listing is effectively a stub.

Warnings

  • —No documentation available — /docs, /pricing, /api, and /README pages all render only 'Connect wallet'
  • —No OpenAPI or output schema describing the response format
  • —The specific resource path (/transactions/252/receipt) suggests a fixed resource rather than a parameterized endpoint; unclear if other transaction IDs are supported
  • —Platform may be a demo or early-stage project

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-19 12:49:51Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-18
Last seen2026-04-24

Agent access

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