Who Uses Osmosis
Depth data for teams that trade at scale
Research desks, treasury teams, and execution operations that need accurate on-chain liquidity context before they move size.
Research Desks
Pre-trade depth analysis for illiquid pairs
A research analyst building a position in a mid-cap DeFi token needs to know whether the depth at a $200K notional is actually $4M or $400K at 1% impact. TVL and 24-hour volume tell you nothing about the available depth at a specific execution size.
Osmosis depth curves let your desk build slippage-adjusted return scenarios rather than assuming execution at mid. For illiquid pairs or thin cross-chain markets, the difference between assumed slippage and actual depth is frequently the difference between a trade that works and one that does not.
Pull depth data via API into your research spreadsheet, or use the dashboard for ad-hoc pair analysis before writing up a trade idea. Depth history gives you a track record of how that pool behaved over the last 90 days, not just how it looks right now.
Treasury Teams
Rebalancing without blowing depth
Protocol treasuries and fund managers moving large on-chain balances face a specific problem: they need to rebalance without moving the market against themselves. A $2M USDC-to-ATOM rebalance on Osmosis DEX at the wrong time, when depth is thin, can cost 3x more in slippage than the same trade during a liquid session.
Osmosis gives your treasury desk a depth window before execution: check the current 1% and 2% depth across routable paths, compare direct execution vs bridged options, and schedule the rebalance for a window when depth supports the notional.
For recurring rebalances, your operations team can pull the same data point at the same time each week via API to build a consistent pre-trade depth check into their workflow. No custom block explorer queries, no stale snapshot data.
Fits how execution teams already work
Osmosis does not ask you to change your stack. It adds accurate depth context to the tools you already use.
Pull depth into your spreadsheet
The REST API returns a JSON object with current depth at 1%, 2%, and 5% impact for any indexed pair. A two-line Python snippet populates a cell in your existing pre-trade model. You do not need a new system.
Compare routing options before execution
The slippage estimator compares direct, bridged, and multi-hop routes for a given notional. Your desk can pick the path with the lowest expected cost, not the one that looks liquid on a volume chart.
Monitor depth over time
Depth history is available in bulk CSV export. Build a time-series view of how depth on your core pairs has evolved, track depth-to-TVL ratios, or backtest whether your historical slippage assumptions were accurate given the actual depth at execution time.
Alert when depth drops below threshold
Enterprise customers can configure depth-threshold alerts via webhook. When the 1% depth on a monitored pair drops below a configured notional, your system receives a notification. Execution windows can be scheduled around depth conditions rather than discovered after execution.
Put accurate depth data in your pre-trade workflow
Start with the Research tier and bring your desk accurate depth curves the same week. No integration required beyond a single API call.