x402-gated account statements endpoint on Base, pay $0.02 per request in USDC.
What it does
This endpoint at lowpaymentfee.com provides access to account statements via a POST request to `/api/v1/accounts/186/statements`. It is part of a broader platform offering data & analytics, AI/ML inference, finance/Web3, and infrastructure utility APIs, all gated behind the x402 payment protocol on the Base network.
The endpoint returns a 402 Payment Required challenge, confirming it is live and operational. Payment is settled in USDC (contract `0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913` on Base) using the "exact" scheme. The maximum amount required per request is 20,000 base units of USDC, which equals $0.02 (USDC uses 6 decimals). The platform advertises uniform $0.02/request pricing across all its endpoints, with no API keys, no rate limits, and no minimum commitments.
Documentation is extremely sparse — the /docs, /api, /pricing, and /README pages all render only a "Connect wallet" prompt with no further content. There is no OpenAPI schema, no request/response examples, and no description of what the account statements endpoint actually returns beyond the generic "Premium API Access" label. The specific endpoint path (`/accounts/186/statements`) suggests it retrieves financial or transactional statements for a particular account ID, but the exact payload format and required POST body are unknown.
Capabilities
Use cases
- —Retrieving account statements or transaction records via a single paid API call
- —Integrating pay-per-request financial data into agent workflows without API key management
- —Programmatic access to account-level financial summaries settled on Base L2
Fit
Best for
- —Agents or applications needing on-demand account statement data with no subscription
- —Developers who prefer crypto-native pay-per-call pricing over traditional API keys
- —Workflows requiring low-cost ($0.02) per-request financial data access
Not for
- —Users who need detailed API documentation or schema guarantees before integrating
- —High-volume batch processing where per-request pricing may add up
- —Anyone without a Base-compatible USDC wallet
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/accounts/186/statements \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-header>"Endpoint
Quality
The endpoint is live (402 challenge confirmed) and pricing is clear ($0.02 USDC on Base). However, there is no OpenAPI schema, no request/response examples, no documentation beyond a wallet-connect prompt, and the purpose of this specific endpoint (account 186 statements) is unclear. Effectively a stub listing.
Warnings
- —No API documentation available — /docs, /pricing, /api, and /README pages all show only 'Connect wallet'
- —No OpenAPI or JSON schema describing request body or response format
- —The endpoint path references a specific account ID (186); unclear if this is parameterizable or fixed
- —No request or response examples available anywhere in crawled content
Citations
- —The endpoint returns a 402 challenge with maxAmountRequired of 20000 base units of USDC on Base networkhttps://lowpaymentfee.com/api/v1/accounts/186/statements
- —Platform advertises $0.02/request pricing with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/accounts/186/statements