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 for a specific account (ID 172) via the x402 payment protocol. It 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, which equals $0.02 per request (USDC uses 6 decimals). No API keys or rate limits are required — callers simply attach an X-PAYMENT header with a valid x402 payment proof.
The provider, lowpaymentfee.com, hosts a broader catalog of x402-payable APIs spanning data & analytics, AI/ML inference (sentiment analysis, summarization, classification, embeddings), finance & Web3 (price feeds, exchange rates, token quotes, gas estimates), and infrastructure utilities (geocoding, validation, conversion, generation). All endpoints are listed at $0.02 per request with the same pay-per-use model on the Base network.
Documentation is extremely sparse — the /docs, /pricing, /api, and /README pages all render only a "Connect wallet" prompt with no further content. There is no OpenAPI schema, no request/response examples, and no description of what the account statements endpoint actually returns or what input it expects in the POST body. The endpoint is confirmed live (returns a proper 402 challenge), but the lack of documentation makes it difficult to use without experimentation.
Capabilities
Use cases
- —Retrieving account statement data for account 172 via programmatic API call
- —Integrating pay-per-request financial data into agent workflows without API key management
- —Demonstrating x402 protocol payment flows on Base network
Fit
Best for
- —Developers experimenting with x402 payment protocol
- —Agents needing on-demand account statement data without subscription commitments
- —Low-volume, pay-as-you-go financial data retrieval
Not for
- —Users needing well-documented APIs with clear request/response schemas
- —High-volume bulk data retrieval where per-request pricing is inefficient
- —Anyone without a Base-network USDC wallet
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/accounts/172/statements \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-proof>"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, and all documentation pages are empty stubs. The purpose of the 'account statements' endpoint is not explained, and the required POST body is unknown. This is effectively a stub listing.
Warnings
- —No documentation available — /docs, /pricing, /api, and /README all show only 'Connect wallet' with no content
- —No OpenAPI or request/response schema provided; POST body format is unknown
- —The specific endpoint path (/api/v1/accounts/172/statements) references a hardcoded account ID (172) with no explanation of what data it returns
- —Provider hosts many listed endpoints but none appear to have public documentation
Citations
- —Endpoint returns 402 with x402 challenge requiring USDC payment on Base networkhttps://lowpaymentfee.com/api/v1/accounts/172/statements
- —USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://lowpaymentfee.com/api/v1/accounts/172/statements
- —maxAmountRequired is 20000 base units ($0.02 USDC)https://lowpaymentfee.com/api/v1/accounts/172/statements
- —Provider lists all endpoints at $0.02/request with no API keys, no rate limitshttps://lowpaymentfee.com
- —Documentation pages (/docs, /pricing, /api, /README) contain only 'Connect wallet' prompthttps://lowpaymentfee.com/docs