Use this page when you need the exact names that appear in SDK configuration, request payloads, or runtime responses.
The name lists on this page are generated from the @illalabs/interfaces constants (scripts/generate-reference.mjs), so they match the shipped SDK version.
Valid autoRouter values today: swapOrBridge: 'lifi' | 'aerodrome', defi.lending: 'aave' | 'morpho', and a perpetuals provider config ('hyperliquid'). The example below shows the common defaults.
Start with the common defaults
Use this as the baseline if you want explicit tool-routing defaults without overriding the rest of the SDK behavior.
tokenTransfer
exchangeRate
getWalletBalance
getConsolidatedWalletBalances
defiFetchListings
defiPositions
defiSupply
defiWithdraw
swap
bridge
predictionMarketsFetch
predictionMarketsGet
predictionMarketsBet
predictionMarketsPositions
predictionMarketsRedeem
predictionMarketsWithdraw
polymarketPostOrder
polymarketPostRedeem
polymarketPostWithdraw
polymarketAuth
polymarketPostGetOrders
polymarketPostCancelOrder
resolveName
perpetualsGetAccountSummary
perpetualsGetPositions
perpetualsPlaceOrder
perpetualsClosePosition
perpetualsUpdateLeverage
hyperliquidDeposit
hyperliquidWithdraw
getPortfolioChart
getTokenPriceChart
getWalletTransactions
These are the names you should expect in pendingTools, tool configs, and provider-specific docs.
Provider keys
- Swap:
lifi, aerodrome (Base-only swaps)
- Bridge:
lifi
- DeFi lending (supply/withdraw/listings/positions):
aave, morpho
- Exchange rates:
coinMarketCap, coingecko, zerion
- Wallet balances:
moralis, polymarket, zerion
- Prediction markets:
polymarket
- Perpetuals:
hyperliquid
- Portfolio / price charts:
zerion
- Transaction history:
zerion
- Name resolution:
ens
Prediction-market redeem flow
Redeem support is a two-step tool sequence:
predictionMarketsRedeem returns a signature request payload for Safe execution.
polymarketPostRedeem submits the signed payload to the relayer.
If your integration executes pendingTools directly, ensure your executor supports signature request handling in addition to transaction handling.
Supported chains
These chains are currently enumerated in the shared interfaces:
Model selection
The SDK exposes model selection through modelContext, and the raw API exposes it through the languageModel request field.
SDK example:
Raw API example:
Use the SDK form when you are calling sdk.sendMessage(...). Use the raw API form only if you are integrating directly with the HTTP API.
Async execution
For operations that continue after submission, use:
IllaSDK.awaitAction(...)
IllaSDK.subscribeToToolStatus(...)
GET /api/v1/actions/check