x402-gated account statements endpoint on Base, paid 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/77/statements`. It is part of a broader platform (lowpaymentfee.com) that offers a variety of x402-protocol pay-per-call APIs spanning data analytics, AI/ML inference, finance, crypto, and utility services — all settled on the Base network using USDC.
The specific endpoint probed here returns an x402 challenge requesting up to 20,000 base units of USDC (0.02 USD, since USDC uses 6 decimals) per request, paid to address `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3`. The platform advertises a flat $0.02/request pricing model with no API keys, no rate limits, and instant access. The response MIME type is `application/json`.
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 spec, no request/response schema documentation, and no examples available. The endpoint is live (402 challenge confirmed), but the actual data returned after payment and the expected POST body are unknown. The endpoint path suggests financial account statement data, but this cannot be verified from available materials.
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 financial data retrieval with on-chain USDC settlement
Fit
Best for
- —Developers wanting keyless, pay-per-use access to account statement data
- —AI agents that can settle x402 payments on Base in USDC
- —Users who prefer micropayment-based API access over subscription models
Not for
- —Users needing detailed API documentation or request/response schemas before integrating
- —High-volume consumers who would benefit from bulk pricing or subscriptions
- —Anyone unable to settle USDC payments on the Base network
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/accounts/77/statements \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-header>"Endpoint
Quality
The endpoint is live and returns a valid x402 challenge, but documentation is effectively nonexistent — all doc pages show only 'Connect wallet'. There is no OpenAPI spec, no request/response schema, no examples, and the purpose of this specific endpoint (account 77 statements) is unclear. The listing is essentially a stub.
Warnings
- —No API documentation available — all doc pages render only 'Connect wallet'
- —No OpenAPI or request/response schema provided
- —The endpoint path references a specific account ID (77); it is unclear whether this is parameterizable or a fixed demo
- —Actual response payload after payment is completely unknown
- —Platform appears to be a generic demo or showcase site with many listed endpoints but no substantive documentation
Citations
- —The endpoint returns a 402 challenge requesting 20,000 base units of USDC on Base networkhttps://lowpaymentfee.com/api/v1/accounts/77/statements
- —Platform advertises $0.02/request pricing with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/accounts/77/statements
- —Docs, API, pricing, and README pages all show only 'Connect wallet' with no further contenthttps://lowpaymentfee.com/docs