Check TWT (Trust Wallet Token) balance via x402-paid API on Base network.
What it does
This endpoint at lowpaymentfee.com returns wallet balance information for TWT (Trust Wallet Token). It is part of a broader suite of pay-per-request APIs offered by the same provider, spanning data analytics, AI/ML inference, finance/Web3 data, and utility services. All endpoints use the x402 payment protocol, settling in USDC on the Base network.
The specific endpoint `/api/v1/wallet/TWT/balance` accepts POST requests and returns JSON. The x402 challenge advertises a maximum cost of 20,000 base units of USDC (asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913, which uses 6 decimals), equating to $0.02 per request. The provider's landing page confirms a flat $0.02/request pricing model across all endpoints, with no API keys, no rate limits, and no minimum commitments required.
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 parameters the endpoint accepts or what fields the response contains. The endpoint is live (returns a proper 402 challenge), but without documentation it is unclear what input the POST body should contain (e.g., a wallet address) or what the response structure looks like.
Capabilities
Use cases
- —Querying TWT token balance for a given wallet address
- —Integrating real-time token balance checks into portfolio dashboards
- —Automated monitoring of Trust Wallet Token holdings
Fit
Best for
- —Agents needing on-demand crypto wallet balance lookups without API key management
- —Developers wanting pay-per-call pricing with no subscription commitment
- —x402-compatible clients settling micropayments in USDC on Base
Not for
- —Users needing detailed transaction history or multi-token batch queries (not documented)
- —Anyone requiring comprehensive API documentation or SDKs before integration
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/wallet/TWT/balance \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402_payment_header>" \
-d '{"address": "0xYourWalletAddress"}'Example
Request
{
"address": "0x1234567890abcdef1234567890abcdef12345678"
}Endpoint
Quality
The endpoint is live and returns a valid x402 challenge with clear pricing ($0.02 USDC on Base). However, documentation is essentially nonexistent — no OpenAPI spec, no request/response schema, no examples. The request body format and response structure are entirely inferred. This is effectively a stub listing.
Warnings
- —No API documentation available — /docs, /pricing, /api, and /README pages all show only 'Connect wallet' with no technical content.
- —Request body schema is unknown; the example_request_json is speculative.
- —Response schema is completely unknown; no example_response_json can be provided.
- —The endpoint path suggests TWT-specific functionality but no details confirm what data is returned.
Citations
- —The endpoint returns a 402 challenge with maxAmountRequired of 20000 base units of USDC on Base networkhttps://lowpaymentfee.com/api/v1/wallet/TWT/balance
- —USDC asset address is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 (6 decimals), so 20000 base units = $0.02https://lowpaymentfee.com/api/v1/wallet/TWT/balance
- —Provider advertises $0.02/request flat pricing with no API keys, no rate limits, and instant access on Base networkhttps://lowpaymentfee.com
- —Provider offers multiple API categories including Data & Analytics, AI & ML, Finance & Web3, and Infrastructurehttps://lowpaymentfee.com