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/53/statements` accepts POST requests and returns JSON. The x402 challenge confirms the endpoint is live, requiring an exact payment of 20,000 base units of USDC (0x8335…2913 on Base), which equals $0.02 given USDC's 6 decimals. Payment is sent to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 with a 300-second timeout. No API keys or rate limits are advertised; access is gated purely by the x402 micropayment.

Documentation is extremely sparse. The crawled /docs, /api, /pricing, and /README pages all returned only a "Connect wallet" prompt with no further content. There is no OpenAPI spec, no request/response schema documentation, and no explanation of what "account 53 statements" actually contains or what POST body parameters are expected. The endpoint appears functional based on the 402 challenge, but without documentation it is difficult to know what data it returns or how to structure requests beyond the bare POST method.

Capabilities

x402-paymentusdc-settlementbase-networkaccount-statementsjson-responsepay-per-request

Use cases

  • Retrieving account statement data via a single micropayment
  • Programmatic access to financial account records without API key management
  • Agent-driven data retrieval with on-chain USDC settlement

Fit

Best for

  • Developers wanting keyless, pay-per-request access to account data
  • AI agents that can settle x402 payments on Base
  • Users who prefer crypto micropayments over subscription billing

Not for

  • Anyone needing well-documented request/response schemas before integrating
  • High-volume batch retrieval where per-request pricing is inefficient
  • Users without USDC on the Base network

Quick start

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

Endpoint

Transporthttp
Protocolx402
Pay to0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3
CurrencyUSD COIN

Quality

0.30/ 1.00

The x402 challenge is live and pricing is clear ($0.02 USDC on Base), but there is zero documentation: no OpenAPI spec, no request/response schemas, no explanation of what the endpoint returns. The docs, pricing, and README pages are all empty beyond a wallet-connect prompt. The specific resource path (accounts/53/statements) is not mentioned anywhere on the site's landing page, making it unclear what data this endpoint actually serves.

Warnings

  • No documentation available — /docs, /api, /pricing, and /README pages are all empty
  • No OpenAPI or request/response schema provided
  • The endpoint path references a specific account ID (53); unclear if this is parameterized or fixed
  • Purpose of 'account statements' is undocumented — could be financial, could be placeholder data
  • Cannot verify what data is actually returned without making a paid request

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-19 00:35:57Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-18
Last seen2026-04-29

Agent access

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