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/81/statements`. It is part of a broader platform offering dozens of x402-payable API endpoints spanning data analytics, AI/ML inference, finance/Web3 data, and infrastructure utilities — all priced at $0.02 per request settled in USDC on the Base network.
The specific endpoint probed here (`/accounts/81/statements`) returns a 402 challenge with `maxAmountRequired` of 20000 base units of USDC (0x8335…2913 on Base, 6 decimals), which equals $0.02. Payment is made via the x402 protocol's `exact` scheme: callers attach an `X-PAYMENT` header containing a signed payment authorization, and the server fulfills the request upon verification. No API keys, rate limits, or upfront commitments are required.
Documentation on the site is extremely thin — the docs, pricing, API, and README pages all render only a "Connect wallet" prompt with no further content. There is no OpenAPI spec, no request/response schema, and no example payloads available. The endpoint's purpose ("account statements") and the meaning of the account ID `81` are not explained anywhere in the crawled material. Because of this, the actual data returned and the expected POST body are unknown and must be discovered by making a paid request.
Capabilities
Use cases
- —Retrieving account statement data via a single paid API call
- —Programmatic access to financial account records without subscription
- —Agent-driven data retrieval with automatic USDC micropayments on Base
Fit
Best for
- —Developers wanting pay-per-use account data without API key management
- —AI agents that can settle x402 payments autonomously on Base
- —Low-volume or exploratory access to statement data without commitments
Not for
- —Users needing detailed API documentation or schema before purchasing
- —High-volume bulk data retrieval where per-request pricing is inefficient
- —Anyone without a Base-compatible USDC wallet
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/accounts/81/statements \
-H "X-PAYMENT: <x402-signed-payment-header>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live and returns a valid x402 402 challenge, confirming it is operational. However, there is no documentation, no OpenAPI spec, no request/response schema, and no explanation of what 'accounts/81/statements' actually returns. The crawled docs/pricing/API pages are all blank beyond a wallet-connect prompt. This is effectively a stub listing.
Warnings
- —No documentation available — docs, pricing, API, and README pages all render only 'Connect wallet' with no content.
- —No request body schema or response schema is provided; the expected POST payload is unknown.
- —The meaning of account ID 81 and what 'statements' data is returned are unexplained.
- —The broader platform lists many endpoints but none have documented schemas or examples.
Citations
- —The endpoint returns a 402 challenge with maxAmountRequired of 20000 base units of USDC on Base (exact scheme).https://lowpaymentfee.com/api/v1/accounts/81/statements
- —The platform advertises $0.02 per request pricing with no API keys, no rate limits, and instant access on Base network.https://lowpaymentfee.com
- —The USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913.https://lowpaymentfee.com/api/v1/accounts/81/statements
- —Docs, pricing, API, and README pages render only a 'Connect wallet' prompt with no further content.https://lowpaymentfee.com/docs