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/179/statements`. It is part of a broader platform offering dozens of x402-protocol pay-per-call APIs spanning data analytics, AI/ML inference, finance/Web3 data, and infrastructure utilities — all priced at $0.02 per request.
Payment is settled on the Base network using USDC (contract `0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913`) via the x402 "exact" scheme. The 402 challenge advertises a `maxAmountRequired` of 20,000 base units, which at 6 decimals equals $0.02. No API keys are required; callers simply attach an `X-PAYMENT` header with a valid x402 payment proof. The endpoint returns `application/json`.
The specific endpoint listed here (`/accounts/179/statements`) appears to be an account-specific financial statements resource. However, documentation beyond the landing page is extremely thin — the docs, API, pricing, and README pages all render only a "Connect wallet" prompt with no further detail. There is no OpenAPI schema, no request/response examples, and no description of what fields the statements endpoint accepts or returns. Prospective callers should be aware that the exact request body format and response structure are undocumented.
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 managing API keys or subscriptions
Fit
Best for
- —Agents or developers who want keyless, pay-per-use access to account statements
- —Crypto-native applications settling microtransactions on Base in USDC
- —Prototyping workflows that need on-demand financial data without subscription commitments
Not for
- —Users who need detailed API documentation or OpenAPI specs before integrating
- —High-volume batch retrieval where per-request pricing becomes costly
- —Applications that cannot handle x402 payment negotiation or USDC on Base
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/accounts/179/statements \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-proof>"Endpoint
Quality
The endpoint is live and returns a valid x402 402 challenge with clear pricing and network info. However, there is no OpenAPI schema, no request/response examples, and all documentation pages beyond the landing page are empty ('Connect wallet' only). The specific purpose of the /accounts/179/statements resource is unclear and undocumented.
Warnings
- —No API documentation available — docs, API, pricing, and README pages all show only 'Connect wallet'
- —No OpenAPI or JSON schema describing request body or response format
- —The endpoint path includes a hardcoded account ID (179); unclear if this is parameterizable or a demo
- —No request or response examples available anywhere in crawled content
Citations
- —The endpoint returns HTTP 402 with x402 challenge advertising maxAmountRequired of 20000 base units in USDC on Basehttps://lowpaymentfee.com/api/v1/accounts/179/statements
- —USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Base networkhttps://lowpaymentfee.com/api/v1/accounts/179/statements
- —Platform pricing is $0.02 per request with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com
- —The platform offers APIs across data/analytics, AI/ML, finance/Web3, and infrastructure categorieshttps://lowpaymentfee.com