Query AVAX wallet balances via x402 micropayment on Base for $0.02 per request.
What it does
This endpoint at lowpaymentfee.com returns AVAX wallet balance data, accessible through the x402 payment protocol. It requires no API keys or account registration — callers pay $0.02 per request in USDC on the Base network via an x402 payment header. The endpoint accepts POST requests and returns JSON.
The provider (lowpaymentfee.com) hosts a broad catalog of pay-per-call APIs spanning data analytics, AI/ML inference, finance/Web3, and infrastructure utilities, all priced uniformly at $0.02 per request. This specific endpoint sits under the crypto/finance category and is designed to retrieve balance information for AVAX (Avalanche) wallets. However, the crawled documentation pages are essentially empty (showing only "Connect wallet"), so the exact request schema (e.g., what parameters to pass for the wallet address) and response format are not documented in any publicly available material.
Because the x402 challenge was successfully captured (HTTP 402 with a well-formed accepts block), the endpoint is confirmed live. Payment settles to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3 using USDC (contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) on Base, with a max amount of 20,000 base units (i.e., $0.02 given USDC's 6 decimals). The timeout for payment settlement is 300 seconds.
Capabilities
Use cases
- —Querying AVAX wallet balances programmatically without API key management
- —Building portfolio trackers that need on-demand balance lookups
- —Agent-driven workflows that need to check Avalanche balances before executing transactions
- —Integrating wallet balance checks into dashboards with micropayment-based access
Fit
Best for
- —Developers needing quick, keyless access to AVAX balance data
- —AI agents that can settle x402 payments autonomously on Base
- —Low-volume or sporadic balance queries where per-call pricing is cheaper than a subscription
Not for
- —High-frequency balance polling where per-call costs would accumulate quickly
- —Users who need detailed AVAX transaction history or token-level breakdowns (not indicated by this endpoint)
- —Callers who cannot settle USDC payments on the Base network
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/wallet/AVAX/balance \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-token>" \
-d '{"address": "0xYourAvaxWalletAddress"}'Example
Request
{
"address": "0x1234567890abcdef1234567890abcdef12345678"
}Endpoint
Quality
The x402 challenge is live and well-formed, confirming the endpoint exists and pricing is clear ($0.02 USDC on Base). However, documentation pages are empty, there is no OpenAPI schema, no example responses, and the request body format is entirely inferred. The endpoint's actual behavior and response structure are unknown.
Warnings
- —Documentation pages (/docs, /api, /pricing, /README) all return only 'Connect wallet' with no usable content.
- —Request body schema is inferred (address field) — no official documentation exists to confirm required parameters.
- —Response format is completely unknown; example_response_json is null.
- —The provider hosts many endpoints all at $0.02 with no visible documentation for any of them, raising questions about maturity.
Citations
- —Endpoint returns HTTP 402 with x402 challenge, confirming it is livehttps://lowpaymentfee.com/api/v1/wallet/AVAX/balance
- —Price is $0.02 per request (maxAmountRequired 20000 base units of USDC with 6 decimals)https://lowpaymentfee.com
- —Payment settles in USDC on Base network to address 0x1A2B13E97f5F837C8F9FA1F95a1484B7C70d85F3https://lowpaymentfee.com/api/v1/wallet/AVAX/balance
- —Provider advertises $0.02/request uniform pricing with no API keys, no rate limitshttps://lowpaymentfee.com