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/196/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 utility services — all gated behind the x402 payment protocol on the Base network.
The specific endpoint probed returns a 402 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 platform'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 input parameters it expects. The endpoint path suggests it retrieves financial statements for a specific account (ID 196), but this is inference only.
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 workflows that need on-demand account data with crypto micropayments
Fit
Best for
- —Developers or agents wanting keyless, pay-per-call access to account statements
- —Crypto-native applications that can settle USDC on Base
- —Low-volume or sporadic usage where $0.02/call flat pricing is attractive
Not for
- —Users who need detailed API documentation or schema guarantees before integrating
- —High-volume batch retrieval where per-call pricing adds up quickly
- —Non-crypto users who cannot settle payments on the Base network
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/accounts/196/statements \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-header>"Endpoint
Quality
The endpoint is live and returns a valid x402 402 challenge with clear pricing. However, there is no OpenAPI schema, no request/response examples, and no meaningful documentation — docs pages render only 'Connect wallet'. The purpose of this specific endpoint (account 196 statements) is unclear and undocumented.
Warnings
- —No OpenAPI or schema documentation available for this endpoint
- —All documentation pages (docs, API, pricing, README) render only 'Connect wallet' with no content
- —The endpoint path references a specific account ID (196); it is unclear whether this is a demo or a real resource
- —No request body schema or response format is documented anywhere
- —The broader platform lists many API categories but none appear to include an 'accounts/statements' endpoint in the landing page catalog
Citations
- —The endpoint returns a 402 challenge with maxAmountRequired of 20000 base units in USDC on Basehttps://lowpaymentfee.com/api/v1/accounts/196/statements
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/accounts/196/statements
- —Platform advertises $0.02/request flat pricing with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com
- —Documentation pages render only 'Connect wallet' with no substantive contenthttps://lowpaymentfee.com/docs