The router can dispatch legs to the venues below. The DexId value appears in routePlan.routes[].legs[].dex on every quote response, and you can pass any subset of these in the optional allowedDexes field on /quote and /execute to restrict routing.
Constant-product (V2-style)
Single-hop direct-pool swaps via the V2 product formula x × y = k.
Concentrated liquidity (V3-style)
Tick-aware pool math.
Universal router (V4-style)
Uniswap V4 is dispatched through the universal-router commands ABI.
Stable and curve-style
Proprietary on-chain AMMs
These are direct integrations with project-specific AMMs on Base. All dispatch through a router contract per protocol.
Other on-chain venues
Restricting routing
If you want to limit which venues the optimizer considers (e.g. for a benchmarking experiment, or to avoid a specific protocol), pass allowedDexes on /quote or /execute:
Restricting allowedDexes reduces routing flexibility. Expect worse expectedAmountOut than an unrestricted quote. Use only when you have a clear reason.
What’s NOT supported
Off-chain professional market makers (PMMs) used by some upstream aggregators are not in this list.
Bridges, cross-chain venues, and limit-order books are also out of scope; this aggregator is same-chain spot routing on Base. 