Resolve user-facing blockchain entities into query-ready identifiers, with ambiguity kept explicit.
COMMON USER ASKS:
- Resolve USDC on Base
- Resolve WETH on Ethereum
- Resolve BAYC contract
FIRST CHOICE FOR:
- resolving a token symbol like USDC to token contract addresses
- resolving EVM contract aliases, protocol names, pool identifiers, or Hyperliquid coin names before querying
- checking which token-list addresses a symbol maps to before querying logs or transfers
- turning a user-friendly token name into deterministic EVM filters
WHEN TO USE:
- The user names a token symbol such as USDC, WETH, DAI, or PEPE and you need contract addresses before querying raw data.
- The user names a well-known EVM contract, protocol, pool identifier, or Hyperliquid ticker and you need a deterministic follow-up filter.
- You need to disambiguate bridged token variants on an EVM network.
- You want a source-backed token address rather than relying on memory or hardcoded constants.
DON'T USE:
- You already have the exact address, pool id, protocol slug, or coin filter and can pass it directly.
EXAMPLES:
- Resolve USDC on Base: {"network":"base-mainnet","kind":"token","query":"USDC","limit":10}
- Resolve WETH on Ethereum: {"network":"ethereum-mainnet","kind":"token","query":"WETH","limit":5}
- Resolve BAYC contract: {"network":"ethereum-mainnet","kind":"contract","query":"bored apes"}
- Resolve Hyperliquid coin: {"kind":"hyperliquid_coin","query":"bitcoin"}