x402basequality 0.30

x402-gated transaction receipt endpoint on Base, paid per-call in USDC.

Price
0.02 USDC / call
Protocol
x402
Verified
no

What it does

This endpoint at lowpaymentfee.com provides a transaction receipt resource (transaction ID 18) behind an x402 paywall. It is part of a broader platform that advertises multiple API categories including Data & Analytics, AI & Machine Learning, Finance & Web3, and Infrastructure utilities — all gated via x402 micropayments on the Base network using USDC.

The specific endpoint `/api/v1/transactions/18/receipt` accepts POST requests and returns JSON. The x402 challenge indicates a maximum payment of 20,000 base units of USDC (0x8335…2913 on Base), which equals $0.02 per request (USDC uses 6 decimals). The platform advertises 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, /pricing, /api, 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 usage examples available. The endpoint is confirmed live (returns a proper 402 challenge), but without documentation it is unclear what request body is expected or what the receipt response contains. The platform appears to be a demonstration or early-stage x402 API marketplace.

Capabilities

x402-paymentusdc-micropaymentbase-networktransaction-receiptper-call-billingno-api-keyjson-response

Use cases

  • Retrieving transaction receipts via micropayment-gated API calls
  • Demonstrating x402 protocol payment flows on Base network
  • Integrating pay-per-call APIs without API key management

Fit

Best for

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

Not for

  • Production workloads requiring documented request/response schemas
  • Users who need detailed API documentation or SDKs
  • High-volume use cases where per-call pricing is inefficient

Quick start

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

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.30/ 1.00

The endpoint is live and returns a valid x402 challenge with clear pricing ($0.02 USDC on Base). However, documentation is effectively nonexistent — all doc pages show only 'Connect wallet'. There is no OpenAPI spec, no request/response schema, no examples, and the specific purpose of this 'transaction 18 receipt' endpoint is unclear. The listing is essentially a stub.

Warnings

  • No API documentation available — all doc pages render only 'Connect wallet'
  • No OpenAPI or schema definition found
  • Purpose of '/api/v1/transactions/18/receipt' is unclear — may be a demo or placeholder
  • No request body schema or response schema documented
  • Platform appears to be early-stage or a demonstration site

Citations

Provenance

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

Agent access