Check account balance via x402 micropayment on Base network for $0.02 per request.
What it does
This endpoint at lowpaymentfee.com provides account balance information behind an x402 paywall. The specific resource `/api/v1/accounts/168/balance` accepts POST requests and returns JSON. Payment is settled in USDC on the Base network at $0.02 per call (20,000 base units with 6 decimals). No API keys or rate limits are required — access is granted per-request via the x402 payment protocol.
The provider lowpaymentfee.com hosts a broader suite of pay-per-call APIs spanning data & analytics (metrics, reports, data export, insights), AI & machine learning (sentiment analysis, text 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 x402/USDC-on-Base payment model.
Documentation is extremely sparse. The docs, API, pricing, and README pages all render only a "Connect wallet" prompt with no further technical detail. There is no OpenAPI schema, no request/response examples, and no description of what fields the balance endpoint accepts or returns. The endpoint is confirmed live (returns a proper 402 challenge), but the actual functionality behind the paywall is unverifiable from public materials alone.
Capabilities
Use cases
- —Querying account balance data without needing API key registration
- —Programmatic balance lookups settled instantly via USDC on Base
- —Agent-driven financial data retrieval using x402 micropayments
Fit
Best for
- —Developers wanting zero-signup API access to balance data
- —AI agents that can settle x402 payments autonomously
- —Users who prefer per-request pricing over subscriptions
Not for
- —Users needing detailed API documentation or schema guarantees before paying
- —High-volume consumers who would benefit from bulk pricing or subscriptions
- —Anyone requiring non-crypto payment methods
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/accounts/168/balance \
-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 zero documentation on request parameters, response schema, or what 'account 168 balance' actually represents. Docs pages are empty beyond a wallet-connect prompt. Without any schema, examples, or functional description, this is effectively a stub listing.
Warnings
- —No OpenAPI schema or request/response documentation available
- —All documentation pages (docs, API, pricing, README) render only 'Connect wallet' with no content
- —The specific meaning of 'accounts/168/balance' is unclear — it is unknown what account or balance type this refers to
- —Functionality behind the paywall cannot be verified without making a paid request
Citations
- —Endpoint returns a 402 challenge with x402Version 1, accepting USDC on Base networkhttps://lowpaymentfee.com/api/v1/accounts/168/balance
- —maxAmountRequired is 20000 base units of USDC (6 decimals) = $0.02https://lowpaymentfee.com/api/v1/accounts/168/balance
- —Provider lists all APIs at $0.02/request with no API keys, no rate limits, and instant accesshttps://lowpaymentfee.com
- —Provider offers APIs across data & analytics, AI & ML, finance & Web3, and infrastructure categorieshttps://lowpaymentfee.com
- —Docs, API, pricing, and README pages contain only a 'Connect wallet' prompthttps://lowpaymentfee.com/docs