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/131/statements`. It is part of a broader platform (lowpaymentfee.com) that offers a variety of x402-protocol APIs spanning data analytics, AI/ML inference, finance/Web3 data, and infrastructure utilities — all payable per-request in USDC on the Base network with no API keys or rate limits required.
The specific endpoint probed here returns an x402 challenge requesting up to 20,000 base units of USDC (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 made via the x402 exact scheme, settling to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 with a 300-second timeout.
Documentation on the site is extremely thin — the docs, pricing, API, and README pages all render only a "Connect wallet" prompt with no further content. There is no OpenAPI spec, no request/response schema, and no usage examples available from the crawl. The endpoint's purpose ("account statements") and the meaning of the account ID (131) are not explained anywhere in the available material. The platform appears to be a generic x402 API marketplace, but without documentation it is difficult to assess the actual data returned by this specific endpoint.
Capabilities
Use cases
- —Retrieving account statement data via a single paid API call
- —Integrating per-request paid data access into agent workflows
- —Programmatic access to financial account information without API key management
Fit
Best for
- —Agents or applications that need on-demand account statement data with no subscription
- —Developers wanting x402-native pay-per-call access on Base
- —Scenarios where API-key-free, wallet-authenticated access is preferred
Not for
- —Users needing detailed API documentation or schema guarantees before integration
- —High-volume bulk data retrieval where per-request pricing becomes expensive
- —Use cases requiring non-crypto payment methods
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/accounts/131/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 spec, no request/response schema, no documentation beyond a landing page listing, and the specific purpose of this endpoint (account 131 statements) is unexplained. Effectively a stub listing.
Warnings
- —No API documentation available — docs, pricing, API, and README pages all show only 'Connect wallet' with no content.
- —No request or response schema provided; the data returned by this endpoint is unknown.
- —The meaning of 'accounts/131/statements' is unexplained — it is unclear what account 131 refers to or what statement data is returned.
- —The broader platform lists many endpoints but none have documented schemas or examples.
Citations
- —The endpoint returns an x402 challenge with maxAmountRequired of 20000 base units of USDC on Base networkhttps://lowpaymentfee.com/api/v1/accounts/131/statements
- —The platform advertises $0.02/request flat pricing with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —USDC asset address is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/accounts/131/statements