x402-gated account statements endpoint on Base, pay-per-request with USDC.
What it does
This endpoint at lowpaymentfee.com provides access to account statements via a POST request to `/api/v1/accounts/104/statements`. It is part of a broader platform (lowpaymentfee.com) that offers a variety of pay-per-call APIs spanning data analytics, AI/ML inference, finance/Web3 data, and infrastructure utilities — all gated behind the x402 payment protocol on the Base network.
The specific endpoint probed here returns an x402 challenge requesting payment in USDC (contract `0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913` on Base) with a `maxAmountRequired` of 20,000 base units. Since USDC uses 6 decimals, this translates to $0.02 per request, consistent with the site's advertised flat pricing of $0.02/request across all endpoints. Payment is made via the x402 `exact` scheme to address `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3`, with a 300-second timeout.
The platform advertises no API keys, no rate limits, and instant access. However, documentation is extremely thin — 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 account statements endpoint actually returns or what parameters it accepts. The endpoint path includes an account ID (104), but it is unclear whether this is a fixed demo account or a parameterized path. The lack of documentation makes it difficult to use this endpoint without experimentation.
Capabilities
Use cases
- —Retrieving account statement data via a single paid API call
- —Programmatic access to financial account records without API key management
- —Agent-driven financial data retrieval with on-chain micropayments
Fit
Best for
- —Developers wanting keyless, pay-per-use access to account data
- —AI agents that can settle x402 payments on Base in USDC
- —Prototyping micropayment-gated API workflows
Not for
- —Production use requiring well-documented request/response schemas
- —Users who need free or subscription-based access without crypto wallets
- —High-volume batch retrieval where per-request fees add up
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/accounts/104/statements \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-header>"Endpoint
Quality
The endpoint is live and returns a valid x402 challenge with clear pricing, but there is no documentation, no OpenAPI schema, no request/response examples, and no explanation of what the endpoint actually returns. The docs pages are empty beyond a wallet-connect prompt. This is effectively a stub listing.
Warnings
- —No documentation available — docs, API, pricing, and README pages all show only 'Connect wallet' with no content
- —No OpenAPI or request/response schema provided; request parameters and response format are unknown
- —The endpoint path includes a hardcoded account ID (104); unclear if this is parameterized or fixed
- —Platform appears to list many endpoints but none have documented schemas or examples
Citations
- —The endpoint returns a 402 x402 challenge requesting 20000 base units of USDC on Basehttps://lowpaymentfee.com/api/v1/accounts/104/statements
- —USDC contract address on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/accounts/104/statements
- —Platform advertises $0.02/request flat pricing with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com
- —The site lists APIs across data/analytics, AI/ML, finance/Web3, and infrastructure categorieshttps://lowpaymentfee.com