Check account balance via x402 micropayment on Base network for $0.02 per request.
What it does
This endpoint at lowpaymentfee.com returns account balance information for a specific account (ID 161) via the x402 payment protocol. It is part of a broader platform offering data & analytics, AI/ML inference, finance/Web3, and infrastructure utility APIs, all priced at $0.02 per request and settled in USDC on the Base network.
The endpoint accepts POST requests and requires an X-PAYMENT header containing a valid x402 payment proof. The x402 challenge confirms the endpoint is live, advertising a maxAmountRequired of 20,000 base units of USDC (0x8335…2913 on Base), which equals $0.02 given USDC's 6 decimals. Payment is sent to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 with a 300-second timeout.
The platform advertises no API keys, no rate limits, and instant access. 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 additional technical detail. There is no OpenAPI spec, no request/response schema, and no usage examples available from the crawl. The specific functionality of the /accounts/161/balance endpoint is not documented beyond its title "Premium API Access," making it unclear what fields the response contains or what input parameters (if any) the POST body expects.
Capabilities
Use cases
- —Querying account balance data with per-request USDC micropayments
- —Integrating pay-per-use balance lookups into agent workflows
- —Accessing financial account information without API key registration
Fit
Best for
- —Agents that need on-demand account balance data without subscription commitments
- —Developers testing x402 payment protocol integrations
- —Scenarios requiring keyless, pay-per-request API access on Base
Not for
- —Users needing detailed API documentation or response schemas before integrating
- —High-volume use cases where per-request pricing may add up compared to subscription plans
- —Anyone without a Base-network USDC wallet
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/accounts/161/balance \
-H "X-PAYMENT: <x402-payment-proof>" \
-H "Content-Type: application/json"Endpoint
Quality
The x402 challenge is live and pricing is clear ($0.02/request in USDC on Base). However, there is no OpenAPI spec, no documented request/response schema, no examples, and the docs pages are empty stubs. The specific purpose of the /accounts/161/balance endpoint is undocumented beyond its generic title.
Warnings
- —No OpenAPI or schema documentation available — request body and response format are unknown
- —All documentation pages (/docs, /api, /pricing, /README) render only a 'Connect wallet' prompt with no content
- —The endpoint path includes a hardcoded account ID (161); it is unclear if this is parameterizable or fixed
- —The description 'Premium API Access' is generic and does not explain what data is returned
Citations
- —The endpoint returns HTTP 402 with x402 challenge advertising maxAmountRequired of 20000 base units of USDC on Basehttps://lowpaymentfee.com/api/v1/accounts/161/balance
- —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 on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/accounts/161/balance