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/2/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 listed here appears to serve financial account statement data (account ID 2). Payment is handled via the x402 protocol: callers receive a 402 challenge containing the payment parameters (asset, amount, payTo address), construct a signed USDC payment, and include it in the `X-PAYMENT` header on retry. The max amount required is 20,000 base units of USDC (6 decimals), which equals $0.02. No API keys, rate limits, or upfront commitments are advertised — access is purely pay-per-call.
Documentation on the site is extremely thin. The docs, pricing, API, and README pages all render only a "Connect wallet" prompt with no substantive content. There is no OpenAPI schema, no request/response examples, and no detailed description of what the statements endpoint returns. The platform lists many endpoints on its landing page but provides no further technical documentation for any of them. Prospective users should expect to experiment with the endpoint to discover its input and output formats.
Capabilities
Use cases
- —Retrieving account statement data on a per-request payment basis
- —Integrating pay-per-call financial data into agent workflows
- —Accessing account records without API key registration
Fit
Best for
- —Agents or developers who want keyless, pay-per-call access to account statements
- —x402-compatible wallets and agent frameworks on Base
- —Low-volume or exploratory use cases where subscription APIs are overkill
Not for
- —Users needing detailed API documentation or guaranteed SLAs before integrating
- —High-volume batch retrieval where per-request pricing becomes expensive
- —Anyone without a Base-compatible USDC wallet
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/accounts/2/statements
# Returns 402 with x402 challenge. Parse the challenge, sign a USDC payment
# for 20000 base units ($0.02) to 0x1A2B...85F3 on Base, then retry with:
# -H 'X-PAYMENT: <signed_payment>'Endpoint
Quality
The endpoint is live (402 challenge confirmed) and pricing is clear ($0.02 USDC on Base). However, there is no OpenAPI schema, no request/response examples, and all documentation pages render only a wallet-connect prompt. The purpose of the specific 'accounts/2/statements' endpoint is only inferable from its URL path. This is effectively a stub listing.
Warnings
- —No API documentation available — docs, pricing, API, and README pages all show only 'Connect wallet'
- —No OpenAPI or JSON schema describing request parameters or response format
- —The endpoint path includes a hardcoded account ID ('2'), and it is unclear whether other account IDs are accessible or what authorization model applies
- —No information on error handling, response structure, or data freshness
Citations
- —The endpoint returns a 402 challenge with maxAmountRequired of 20000 base units of USDC on Basehttps://lowpaymentfee.com/api/v1/accounts/2/statements
- —All endpoints are priced at $0.02 per request with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —The platform offers endpoints across Data & Analytics, AI & ML, Finance & Web3, and Infrastructure categorieshttps://lowpaymentfee.com