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/63/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, crypto, and utility services — all gated behind the x402 payment protocol on the Base network.
The specific endpoint probed here charges up to $0.02 per request (20,000 base units of USDC, which has 6 decimals = $0.02), settled in USDC on Base to the address `0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3`. The x402 challenge confirms the endpoint is live and returns `application/json`. No API keys or rate limits are advertised; access is granted purely through the x402 payment header.
Documentation is extremely sparse. The crawled docs, API, pricing, and README pages all rendered only a "Connect wallet" prompt with no substantive content. There is no OpenAPI schema, no request/response examples, and no description of what the "statements" resource actually contains or what parameters the POST body expects. The endpoint path suggests financial account statement retrieval (account ID 63), but the actual data model is unknown. The broader platform lists many endpoints at $0.02 each across categories like sentiment analysis, text summarization, geocoding, and crypto gas estimates, but none have documented schemas.
Capabilities
Use cases
- —Retrieving account statement data via a single paid API call
- —Programmatic access to financial account information without API key management
- —Agent-driven financial data retrieval with automatic USDC micropayments
Fit
Best for
- —Developers or agents needing keyless, pay-per-call access to account statements
- —x402-compatible agents that can settle USDC on Base
- —Use cases where avoiding API key provisioning is valuable
Not for
- —Production use requiring documented request/response schemas
- —Bulk or high-volume statement retrieval where per-call pricing is inefficient
- —Users who need detailed API documentation before integration
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/accounts/63/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 ($0.02 USDC on Base). However, there is no OpenAPI schema, no request/response documentation, no examples, and the docs pages are empty. The purpose of the 'statements' resource for account 63 is unexplained. This is effectively a stub listing.
Warnings
- —No API documentation available — docs, pricing, and README pages all render only a wallet connect prompt
- —No request body schema or response schema documented; callers cannot know what parameters to send
- —The endpoint path references a specific account ID (63), which may not be generalizable
- —No OpenAPI or ai-plugin manifest found
- —The broader platform lists many endpoints but none appear to have published schemas
Citations
- —The endpoint returns a 402 x402 challenge with maxAmountRequired of 20000 in USDC on Basehttps://lowpaymentfee.com/api/v1/accounts/63/statements
- —USDC asset contract on Base: 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/accounts/63/statements
- —Platform advertises $0.02 per request, no API keys, no rate limits, Base networkhttps://lowpaymentfee.com
- —Docs, API, pricing, and README pages render only a Connect wallet prompt with no substantive contenthttps://lowpaymentfee.com/docs