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/151/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 of up to 20,000 base units of USDC (contract `0x8335…2913` on Base). Since USDC uses 6 decimals, this translates to $0.02 per request, consistent with the site's advertised flat pricing of $0.02/request across all endpoints. Payment is settled on-chain to address `0x1A2B…85F3` using the x402 "exact" scheme 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 spec, no request/response schema documentation, and no usage examples available from the crawl. The endpoint path suggests it returns financial statement data for a specific account (ID 151), but the exact request body format and response structure are unknown.
Capabilities
Use cases
- —Retrieving account statement data on a per-request payment basis
- —Programmatic access to financial account records without API key management
- —Agent-driven financial data retrieval using on-chain USDC micropayments
Fit
Best for
- —Developers or agents needing one-off account statement lookups without subscription commitments
- —x402-compatible agents that can settle USDC payments on Base
- —Use cases where keyless, pay-per-call access to financial data is preferred
Not for
- —Users needing detailed API documentation or schema guarantees before integration
- —High-volume batch retrieval where per-request pricing would be costly
- —Anyone without a Base-compatible USDC wallet
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/accounts/151/statements \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-token>"Endpoint
Quality
The endpoint is live and returns a valid x402 challenge with clear pricing, but there is no OpenAPI spec, no request/response schema, and all documentation pages are empty stubs. The purpose of this specific endpoint (account 151 statements) is unclear and undocumented, making integration highly speculative.
Warnings
- —No OpenAPI or schema documentation available — request body format and response structure are completely unknown.
- —All documentation pages (/docs, /api, /pricing, /README) return only a 'Connect wallet' prompt with no content.
- —The endpoint path references a hardcoded account ID (151); it is unclear whether this is a demo, a specific user resource, or parameterizable.
- —The broader platform lists many API categories but none have documented schemas or examples.
Citations
- —The endpoint returns a 402 challenge with maxAmountRequired of 20000 base units of USDC on Base networkhttps://lowpaymentfee.com/api/v1/accounts/151/statements
- —USDC contract address on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/accounts/151/statements
- —Platform advertises $0.02/request flat pricing with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com
- —Documentation pages (/docs, /api, /pricing, /README) render only 'Connect wallet' with no substantive contenthttps://lowpaymentfee.com/docs