x402basequality 0.30

x402-payable account statements endpoint on Base, settled in USDC at $0.02/request.

Price
0.02 USDC / call
Protocol
x402
Verified
no

What it does

This endpoint at lowpaymentfee.com provides account statement data behind an x402 paywall. It is part of a broader platform offering dozens of pay-per-request APIs spanning data analytics, AI/ML inference, finance/Web3 data, and infrastructure utilities — all priced at $0.02 per request and settled in USDC on the Base network.

The specific endpoint `/api/v1/accounts/120/statements` is described as "Premium API Access" and accepts POST requests. The x402 challenge confirms it is live, requiring a maximum of 20,000 base units of USDC (0.02 USD, since USDC uses 6 decimals) per call, paid to address `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3` on Base. The payment scheme is "exact" with a 300-second timeout. No API keys or rate limits are advertised; access is granted purely via the x402 payment header.

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 description of what the statements endpoint actually returns or what parameters it accepts. The endpoint appears to be one of many on a platform designed to demonstrate low-fee x402 micropayments, but the actual data served is unclear.

Capabilities

x402-paymentusdc-settlementbase-networkaccount-statementspay-per-requestno-api-keypost-method

Use cases

  • Retrieving account statement data via a single micropayment
  • Demonstrating x402 payment protocol integration on Base
  • Agent-driven financial data retrieval without API key management

Fit

Best for

  • Developers experimenting with x402 payment protocol
  • Agents needing keyless, pay-per-call access to account data
  • Micropayment-based API consumption on Base L2

Not for

  • Production use requiring documented request/response schemas
  • High-volume batch retrieval where per-request pricing is inefficient
  • Users who need detailed API documentation before integrating

Quick start

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

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, but there is no OpenAPI schema, no request/response documentation, no examples, and no explanation of what data the statements endpoint actually returns. The docs pages are empty beyond a wallet-connect prompt. This is effectively a stub listing.

Warnings

  • No OpenAPI or request/response schema available
  • Documentation pages (docs, API, pricing, README) contain no substantive content
  • The actual data returned by the /accounts/120/statements endpoint is undocumented
  • It is unclear whether account ID 120 is a fixed demo or parameterizable
  • Platform appears to be a demonstration/showcase site for x402 micropayments rather than a production data provider

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-19 01:07:11Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-18
Last seen2026-04-29

Agent access