Query SUSHI token wallet balance via x402 micropayment on Base for $0.02 per request.
What it does
This endpoint at lowpaymentfee.com returns the wallet balance for the SUSHI token. It is part of a broader suite of pay-per-call APIs offered by lowpaymentfee.com, spanning data analytics, AI/ML inference, finance/Web3, and infrastructure utilities. All endpoints on the platform use the x402 payment protocol, settling in USDC on the Base network at $0.02 per request.
The specific endpoint `/api/v1/wallet/SUSHI/balance` accepts POST requests and returns JSON. The x402 challenge confirms the endpoint is live, requiring an exact payment of 20,000 base units of USDC (0x8335…2913 on Base), which equals $0.02 given USDC's 6 decimals. No API keys or rate limits are advertised; access is gated purely by the x402 payment header.
Documentation on the site is extremely sparse — the docs, pricing, and API 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. The endpoint's actual response format and accepted parameters are unknown beyond what can be inferred from the URL pattern (a wallet address or identifier may be needed in the POST body). Use with caution until more documentation surfaces.
Capabilities
Use cases
- —Checking the SUSHI token balance for a given wallet address
- —Integrating SUSHI balance lookups into portfolio tracking dashboards
- —Automated monitoring of SUSHI holdings across wallets
Fit
Best for
- —Agents or bots needing on-demand SUSHI balance queries without API key management
- —Developers prototyping crypto portfolio tools who want simple pay-per-call access
- —Micropayment-native workflows on Base that need token balance data
Not for
- —High-frequency balance polling where per-request costs would accumulate quickly
- —Users who need detailed transaction history or multi-token batch queries
- —Anyone requiring well-documented, schema-validated API contracts
Quick start
curl -X POST https://lowpaymentfee.com/api/v1/wallet/SUSHI/balance \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402_payment_token>" \
-d '{"address": "0xYourWalletAddress"}'Example
Request
{
"address": "0x1234567890abcdef1234567890abcdef12345678"
}Endpoint
Quality
The endpoint is live (402 challenge confirmed) and pricing is clear ($0.02 USDC on Base), but there is no OpenAPI spec, no documented request/response schema, no examples, and the docs pages are empty. The request and response formats are entirely inferred.
Warnings
- —No OpenAPI or schema documentation available — request body and response format are unknown
- —Docs, pricing, and API pages on the site render only 'Connect wallet' with no technical content
- —The example request JSON is speculative; actual required fields are undocumented
- —The platform hosts many diverse endpoints (AI, analytics, finance, utils) all at $0.02 — unclear what backend services actually power them
Citations
- —The endpoint returns HTTP 402 with an x402 challenge requiring 20000 base units of USDC on Basehttps://lowpaymentfee.com/api/v1/wallet/SUSHI/balance
- —USDC asset contract on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://lowpaymentfee.com/api/v1/wallet/SUSHI/balance
- —All APIs on the platform are priced at $0.02 per request with no API keys or rate limitshttps://lowpaymentfee.com