x402-payable account statements endpoint on Base, settled in USDC at $0.02 per request.
What it does
This endpoint at lowpaymentfee.com provides access to account statement data via the x402 payment protocol. The specific resource `/api/v1/accounts/30/statements` is a POST endpoint that returns JSON account statements upon payment. It is part of a broader platform (lowpaymentfee.com) that hosts dozens of pay-per-call APIs spanning data analytics, AI/ML inference, finance, crypto, and utility services — all priced at $0.02 per request.
Payment is handled via the x402 protocol on the Base network using USDC (contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913). The maximum amount required per call is 20,000 base units, which equals $0.02 USD (USDC uses 6 decimals). No API keys or rate limits are advertised; access is granted immediately upon valid payment. The endpoint was confirmed live, returning a proper 402 challenge with x402 version 1.
Documentation is extremely sparse. The crawled docs, API, pricing, and README pages all rendered only a "Connect wallet" prompt with no additional technical detail. There is no OpenAPI schema, no request/response examples, and no description of what fields an account statement contains or what parameters the POST body accepts. The endpoint path suggests it retrieves statements for a specific account (ID 30), but it is unclear whether this is a demo account or a parameterized resource. Prospective users should expect to experiment or contact the provider for integration details.
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 services that need on-demand account statement retrieval with crypto micropayments
- —Developers experimenting with x402 protocol integrations on Base
- —Use cases requiring keyless, pay-as-you-go API access
Not for
- —Users who need detailed API documentation or OpenAPI specs before integrating
- —High-volume batch retrieval where per-request pricing is inefficient
- —Users without access to USDC on the Base network
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/accounts/30/statements \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-header>"Endpoint
Quality
The endpoint is confirmed live with a valid 402 challenge and clear pricing ($0.02 USDC on Base). However, there is no OpenAPI schema, no request/response examples, no documentation beyond a wallet-connect prompt, and the purpose of this specific resource (account 30 statements) is unclear. Effectively a stub listing.
Warnings
- —No API documentation available — docs, pricing, and README pages all render only a 'Connect wallet' prompt
- —No OpenAPI or request/response schema provided; request body format is unknown
- —The endpoint path references a specific account ID (30) with no explanation of whether this is parameterized or fixed
- —The broader platform lists many endpoints but none have documented schemas
Citations
- —The endpoint returns a 402 challenge with x402 version 1, maxAmountRequired of 20000 base units in USDC on Basehttps://lowpaymentfee.com/api/v1/accounts/30/statements
- —All APIs on the platform are priced at $0.02 per request with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com
- —USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Base networkhttps://lowpaymentfee.com/api/v1/accounts/30/statements