x402-payable account statements endpoint on Base, settled in USDC at $0.02 per request.
What it does
This endpoint at lowpaymentfee.com provides account statement data behind an x402 paywall. It is part of a broader platform (lowpaymentfee.com) that offers a variety of pay-per-request APIs spanning data analytics, AI/ML inference, finance/Web3 data, and infrastructure utilities — all priced at $0.02 per call and settled in USDC on the Base network.
The specific endpoint `/api/v1/accounts/57/statements` accepts POST requests and returns JSON. Payment is handled via the x402 protocol: callers must include an X-PAYMENT header with a valid payment proof. The challenge advertises a maxAmountRequired of 20,000 base units of USDC (0x8335…2913 on Base), which equals $0.02 given USDC's 6 decimals. The payment scheme is "exact" with a 300-second timeout. No API keys or rate limits are advertised; access is gated purely by micropayment.
Documentation is extremely sparse. The crawled /docs, /api, /pricing, and /README pages all returned only a "Connect wallet" prompt with no substantive content. There is no OpenAPI spec, no request/response schema beyond the x402 outputSchema stub, and no description of what "account statements" contain or what parameters the POST body expects. The endpoint is confirmed live (402 challenge captured), but the lack of documentation makes it difficult to use without additional discovery.
Capabilities
Use cases
- —Retrieving account statement data via a single micropayment
- —Integrating pay-per-request financial data into agent workflows
- —Accessing statement records without API key registration
Fit
Best for
- —Agents or developers who want keyless, pay-per-call access to account statements
- —Crypto-native workflows that can sign x402 payment proofs on Base
- —Scenarios requiring low-friction, no-subscription API access
Not for
- —Users who need detailed API documentation or OpenAPI specs before integrating
- —High-volume batch retrieval where per-request pricing is inefficient
- —Non-crypto workflows that cannot produce x402 payment headers
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/accounts/57/statements \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-proof>"Endpoint
Quality
The endpoint is confirmed live via a valid 402 challenge, and pricing is clear ($0.02 USDC on Base). However, there is no OpenAPI spec, no request/response schema, no documentation beyond a wallet-connect prompt, and no examples. The purpose of 'account statements' for account 57 is unexplained. This is effectively a stub listing.
Warnings
- —No API documentation available — /docs, /api, /pricing, and /README all return only a 'Connect wallet' prompt with no content.
- —No request body schema or response schema documented; callers must guess what POST parameters are accepted.
- —The endpoint path includes a hardcoded account ID (57); it is unclear whether other account IDs are accessible or what they represent.
- —No OpenAPI or ai-plugin manifest found.
Citations
- —The endpoint returns a 402 challenge with maxAmountRequired of 20000 base units of USDC on Base (scheme: exact, timeout: 300s).https://lowpaymentfee.com/api/v1/accounts/57/statements
- —The platform advertises $0.02 per request with no API keys, no rate limits, and instant access on the Base network.https://lowpaymentfee.com
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913.https://lowpaymentfee.com/api/v1/accounts/57/statements