Supported AMMs - Soroswap Finance

Aggregator v3 runs one trade across several Soroban venues, hop by hop, in a single atomic transaction. The Soroswap API picks the routes, and SDEX is quoted alongside as a separate classic path.

Venue	Pool type	Aggregator v3 contract	Routed by the API
Soroswap AMM	Constant product	Yes (`Hop::Soroswap`)	Yes
Aquarius	Constant product, stable, concentrated	Yes (`Hop::Aqua`)	Yes
SushiSwap V3	Concentrated liquidity (Uniswap V3 style)	Yes (`Hop::Sushi`)	Yes
Comet	Weighted pools (Balancer style)	Yes (`Hop::Comet`)	Yes
Phoenix	Constant product, stable	Yes (`Hop::Phoenix`)	Not today
SDEX (Stellar classic order book)	Order book and classic liquidity pools	No	Yes, as a separate path payment

What each column means:

Aggregator v3 contract: the contract can execute a hop on that venue, so you can name such pools in your own routes.
Routed by the API: /quote currently considers that venue. Phoenix is held back while its quoted prices do not hold at execution.
SDEX: a quote with "platform": "sdex" is built as a classic path payment, not an aggregator call.

GET /protocols?network=mainnet returns the venue list the API accepts in protocols. Some assets only trade on one venue. deJTRSY, for example, has its liquidity in SushiSwap V3 pools. When you need such a pair, add that venue to protocols.