x402-payable account statements endpoint on Base, settled in USDC at $0.02/request.
What it does
This endpoint at lowpaymentfee.com provides account statement data behind an x402 paywall. The specific resource `/api/v1/accounts/140/statements` accepts POST requests and returns JSON. Payment is settled on the Base network using USDC (contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) with a maximum cost of 20,000 base units — equivalent to $0.02 per request (USDC uses 6 decimals). No API keys or rate limits are required; access is granted purely via the x402 payment protocol.
The broader lowpaymentfee.com platform advertises a wide catalog of x402-gated APIs spanning data analytics, AI/ML inference (sentiment analysis, summarization, classification, embeddings), finance/crypto market data, and utility services — all priced at $0.02 per request. However, this specific listing covers only the `/api/v1/accounts/140/statements` endpoint. The endpoint's purpose ("account statements") suggests it returns financial or transactional statement records for a given account ID, but no detailed documentation, request schema, or response schema was found in the crawl.
The endpoint is live and returning a valid x402 challenge (HTTP 402 with version 1 accepts block). The payment scheme is "exact" with a 300-second timeout. Documentation pages on the site (/docs, /pricing, /api) returned only a wallet-connect prompt with no substantive content, so the actual request/response format remains unknown.
Capabilities
Use cases
- —Retrieving account statement data programmatically via a single micropayment
- —Integrating pay-per-request financial data into agent workflows without API key management
- —Accessing account records on-demand with USDC settlement on Base
Fit
Best for
- —Agents or applications needing on-demand account statement retrieval without subscription commitments
- —Developers experimenting with x402 payment protocol integrations
- —Use cases requiring keyless, pay-as-you-go API access on Base
Not for
- —Users needing detailed API documentation or guaranteed SLA before integrating
- —High-volume batch processing where per-request pricing may add up
- —Non-crypto workflows that cannot settle payments in USDC on Base
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/accounts/140/statements \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-token>"Endpoint
Quality
The endpoint is live and returns a valid x402 challenge, but there is no documentation, no request/response schema, and no examples available. The purpose of the endpoint ('account statements') is vague and the docs pages are empty. This is effectively a stub listing.
Warnings
- —No request or response schema available — the actual data format is unknown
- —Documentation pages (/docs, /pricing, /api) returned no content beyond a wallet-connect prompt
- —The endpoint path includes a hardcoded account ID (140); it is unclear whether other account IDs are supported or what input is expected
- —The broader platform advertises many endpoints but none have documented schemas
Citations
- —Endpoint returns HTTP 402 with x402 version 1 challenge, confirming it is livehttps://lowpaymentfee.com/api/v1/accounts/140/statements
- —Payment is 20,000 base units of USDC on Base (asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913), equaling $0.02https://lowpaymentfee.com/api/v1/accounts/140/statements
- —Platform advertises $0.02/request pricing with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —Multiple API categories listed: Data & Analytics, AI & ML, Finance & Web3, Infrastructurehttps://lowpaymentfee.com