Check TON wallet balances via x402 micropayment — $0.02 per request on Base.
What it does
This endpoint at lowpaymentfee.com returns the balance of a TON (The Open Network) wallet. It is part of a broader suite of pay-per-call APIs offered by the same provider, spanning data analytics, AI/ML inference, finance/Web3, and utility services. All endpoints use the x402 payment protocol, settling in USDC on the Base network at $0.02 per request.
The specific endpoint `/api/v1/wallet/TON/balance` accepts POST requests and returns JSON. The x402 challenge confirms it 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.
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 spec, no request/response schema, and no usage examples available from the crawled material. The endpoint is confirmed live via the 402 challenge, but the actual request body format and response structure must be inferred from the URL path (likely requires a TON wallet address in the POST body).
Capabilities
Use cases
- —Querying the balance of a TON wallet address programmatically
- —Building portfolio trackers that include TON holdings
- —Automated monitoring of TON wallet balances for bots or agents
- —Integrating TON balance data into multi-chain dashboards
Fit
Best for
- —Agents or apps that need on-demand TON balance lookups without API key management
- —Developers wanting pay-per-call crypto data without subscriptions
- —x402-compatible AI agents that can settle micropayments on Base
Not for
- —High-frequency polling where $0.02/request adds up quickly
- —Users who need detailed TON transaction history or NFT data beyond simple balances
- —Anyone without a Base-network USDC wallet to settle x402 payments
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/wallet/TON/balance \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402-payment-header>" \
-d '{"address": "EQD...your_TON_address"}'Example
Request
{
"address": "EQDtFpEwcFAEcRe5mLVh2N6C0x-_hJEM7W61_JLnSF74p4q2"
}Endpoint
Quality
The endpoint is confirmed live via a valid x402 402 challenge, 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 all documentation pages return only a wallet-connect prompt. The request body and response format are entirely inferred.
Warnings
- —No OpenAPI or schema documentation available — request/response formats are inferred from the URL path
- —All doc pages (docs, API, pricing, README) render only 'Connect wallet' with no technical content
- —Example request JSON is speculative; actual required fields are unknown
- —No information on what fields the response contains or error handling
Citations
- —The endpoint returns a 402 challenge with maxAmountRequired of 20000 base units of USDC on Base networkhttps://lowpaymentfee.com/api/v1/wallet/TON/balance
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/wallet/TON/balance
- —All APIs are priced at $0.02 per request with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —The provider offers APIs across Data & Analytics, AI & ML, Finance & Web3, and Infrastructure categorieshttps://lowpaymentfee.com