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

What it does

This x402-enabled endpoint at lowpaymentfee.com provides a "Premium API Access" transaction receipt via a POST request. It is part of a broader platform offering multiple API categories — data & analytics, AI & machine learning, finance & Web3, and infrastructure utilities — all priced uniformly at $0.02 per request, settled in USDC on the Base network.

The specific probed endpoint (`/api/v1/transactions/1/receipt`) returns a 402 Payment Required challenge requesting up to 20,000 base units of USDC (0x8335…2913 on Base, 6 decimals = $0.02) per call. Payment is made via the x402 exact scheme with no API keys or rate limits required. The platform advertises instant access and a simple pay-per-use model with no minimums or commitments.

Documentation is extremely sparse — 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 available from the crawl. The endpoint is live (402 challenge confirmed), but the actual data returned after payment is unknown. The broader platform lists 16 endpoints across four categories, but none have documented schemas or sample responses.

Capabilities

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

Use cases

  • —Retrieving transaction receipts on a per-call payment basis
  • —Demonstrating x402 payment protocol integration
  • —Agent-driven API consumption without API key management

Fit

Best for

  • —Developers experimenting with x402 payment protocol
  • —Agents that need keyless, pay-per-call API access on Base
  • —Low-volume, on-demand transaction receipt retrieval

Not for

  • —Production workloads requiring documented request/response schemas
  • —High-volume batch processing where per-call pricing is inefficient
  • —Users without USDC on Base network

Quick start

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

Endpoint

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

Quality

0.30/ 1.00

The endpoint is live and returns a valid x402 402 challenge, but documentation is effectively nonexistent — every doc page renders only 'Connect wallet'. There is no OpenAPI spec, no request/response schema, no examples, and the actual functionality behind the receipt endpoint is undocumented. The listing is essentially a stub with confirmed liveness.

Warnings

  • —No documentation available — all doc pages render only 'Connect wallet'
  • —No OpenAPI or schema specification found
  • —No request body or response body examples available
  • —Actual data returned by the receipt endpoint after payment is unknown
  • —The endpoint path includes a hardcoded ID '/transactions/1/receipt' — unclear if parameterizable

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-19 12:01:59Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-18
Last seen2026-04-25

Agent access

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