TorqueTorque

Search docs

Search Torque documentation pages & sections

Get API KeyEnter App

29 Protocols Supported

Torque connects to 29 DeFi protocols across lending, trading, and bridging. Lend venues are chain-scoped execution paths; trading and bridge names are aggregators Enso may route through. Pair with Chains & Assets when you need network coverage or token contract metadata.

Categories

Showing 30 of 30 protocol listings

Lend / Borrow

ProtocolCategory
AaveLend / Borrow
JupiterLend / Borrow
KaminoLend / Borrow
MorphoLend / Borrow

Trading / Swaps

ProtocolCategory
0xTrading / Swaps
1inchTrading / Swaps
BarterTrading / Swaps
BebopTrading / Swaps
ECOTrading / Swaps
EisenTrading / Swaps
FlyTrading / Swaps
FyndTrading / Swaps
HyperliquidTrading / Swaps
JupiterTrading / Swaps
KyberSwapTrading / Swaps
MagpieTrading / Swaps
OdosTrading / Swaps
OndoTrading / Swaps
OpenOceanTrading / Swaps
ParaSwapTrading / Swaps
SushiSwapTrading / Swaps
UniswapTrading / Swaps

Bridges

ProtocolCategory
AcrossBridges
EnsoBridges
GasZipBridges
MayanBridges
RelayBridges
SquidBridges
StargateBridges
SymbiosisBridges

FAQ

Is this page a user-facing protocol picker?

No. Users pick product buckets and intents (USD, ETH, lend, swap). This page lists DeFi venues and aggregators Torque may route through at execution. Integrators do not ask users to choose Uniswap vs 1inch.

What is the difference between Lend / Borrow, Trading / Swaps, and Bridges?

Lend / Borrow names are chain-scoped venues Torque can execute against (Aave, Morpho, Kamino). Trading / Swaps and Bridges are aggregator and bridge routes Enso may use under the hood when settling a wallet_order. See Architecture for how routing connects.

Do users pick a protocol for swaps or lends?

No. Users express an intent; Torque drafts a wallet_order and routing picks the venue or aggregator. Pair with Assets for what users hold and Chains for network coverage.

Why do trading and bridge rows look like aggregators?

Because they are. Names like 1inch, Odos, Stargate, and Across are routing options Enso may use when composing settlement. Presence on this list means Torque can route through that name, not that your UI exposes it as a picker.

What does supported mean for the Assistant?

For money-moving intents, supported means Torque can draft a wallet_order whose settlement may use these venues. Assistant and Actions talk in product buckets and intents; protocol selection stays in the routing layer.

Questions or corrections? hello@torque.fi