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/171/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 is live and returns a standard x402 challenge (HTTP 402) requiring payment in USDC (contract `0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913` on Base). The maximum amount required per request is 20,000 base units of USDC, which equals $0.02 (USDC uses 6 decimals). Payment is made via the `exact` scheme to address `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3`, with a timeout of 300 seconds. No API keys or rate limits are advertised; access is instant upon payment.
Documentation is extremely sparse — the docs, API, pricing, and README pages all render only a "Connect wallet" prompt with no further content. The specific input schema for the POST body and the response format for account statements are not documented anywhere in the crawled material. The endpoint path suggests it retrieves statements for a specific account (ID 171), but it is unclear whether this is a demo account, a parameterized path, or a fixed resource. Use with caution until more documentation becomes available.
Capabilities
Use cases
- —Retrieving account statement data on a pay-per-request basis
- —Integrating financial statement access into agent workflows without API key management
- —Programmatic access to account records settled via on-chain USDC on Base
Fit
Best for
- —Agents or services needing on-demand account statement retrieval without subscription commitments
- —Developers experimenting with x402 payment-gated APIs on Base
- —Low-volume, pay-as-you-go financial data access
Not for
- —High-volume bulk data retrieval where per-request costs add up
- —Users who need detailed API documentation or guaranteed SLAs before integrating
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/accounts/171/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. However, there is no documentation for the request body schema, response format, or what 'account 171 statements' actually returns. 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.
- —The specific endpoint path `/api/v1/accounts/171/statements` has a hardcoded account ID (171); it is unclear if this is parameterized or fixed.
- —No input or output schema is documented; the POST body format is unknown.
- —The endpoint is not listed among the advertised APIs on the landing page, raising questions about its intended use.
Citations
- —The endpoint returns a 402 challenge with maxAmountRequired of 20000 base units of USDC on Base networkhttps://lowpaymentfee.com/api/v1/accounts/171/statements
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/accounts/171/statements
- —Platform advertises $0.02 per request, no API keys, no rate limits, instant access on Base networkhttps://lowpaymentfee.com
- —Docs, API, pricing, and README pages render only 'Connect wallet' with no additional contenthttps://lowpaymentfee.com/docs