The Platform

The Osmosis platform

Cross-chain liquidity depth and routing slippage, computed at the pool level.

Chain and protocol coverage

Osmosis indexes pool state continuously across the following chains and DEX protocols. Depth is computed at the pool level, not aggregated at the chain level, so your analysis reflects actual available liquidity for each token pair.

CosmosOsmosis DEXATOM, OSMO, and IBC-bridged token pairs across superfluid and standard pools
Ethereum mainnetUniswap v3Concentrated liquidity pools: ETH/USDC, WBTC/ETH, and major ERC-20 pairs
Ethereum mainnetCurve FinanceStablecoin and liquid staking derivative pools with deep depth at tight spreads
Arbitrum OneArbitrumUniswap v3 and native Arbitrum DEX pools: ARB/USDC and bridged pairs
Polygon PoSPolygonMATIC/USDC and major bridged token pairs across QuickSwap and Uniswap v3 pools
Visual representation of cross-chain data coverage spanning multiple blockchain networks

Liquidity depth measurement

Most on-chain analytics tools report TVL or 24-hour volume. Osmosis measures something different: the depth curve. For each indexed pool, we compute the available liquidity at three standard price impact thresholds: 1%, 2%, and 5%. This tells you how much of a given token pair you can execute before the price moves by that amount.

Depth is not static. Osmosis tracks the rate of change in pool depth between measurement intervals, so your research stack can distinguish between a pool with stable depth and one that is draining. Depth velocity catches deteriorating liquidity windows before they affect your execution.

$4.2M
1%
$6.8M
2%
$11.3M
5%

ATOM/USDC, Osmosis DEX (sample)

Routing slippage estimates

Given a trade notional and target token pair, Osmosis estimates expected slippage across available routing paths: direct execution in a single pool, bridged paths through an intermediate chain, and multi-hop routes through two or more pools. The estimates use the current depth curve, not a historical average, so they reflect what execution would cost right now.

Block explorer snapshot data misses intraday depth change. A depth reading pulled at 09:00 UTC may not reflect the pool state at 11:30 UTC when execution happens. Osmosis continuous indexing closes that gap: depth is always the most recently computed value, not a stale export.

Route Notional Est. Slippage Depth Used
Direct: ETH/USDC, Uniswap v3 $500K 0.18%best $18.1M @ 1%
Bridge: ETH to Cosmos, OSMO/USDC $500K 0.74% $4.2M @ 1%
Multi-hop: ARB/USDC then bridge $500K 1.42% $2.9M @ 1%

Get your data out

Osmosis delivers depth data in three formats. Your tier determines which delivery methods are available.

CSV Export

Download bulk depth snapshots in structured CSV format. Column schema is consistent across chains so you can merge multi-chain exports without reformatting. Up to 500 rows/day on the Research tier, unlimited on Pro and Enterprise.

Research, Pro, Enterprise

REST API

Query current depth and slippage estimates programmatically. Standard REST endpoints return JSON, documented with OpenAPI spec. 10,000 calls/day on Pro. Enterprise plans include higher rate limits and custom endpoint configuration.

Pro, Enterprise

Dashboard

Browser-based depth viewer. Browse indexed chains, search by token pair, view depth curves and slippage estimates without writing code. Included on all tiers. Useful for ad-hoc queries and for teams where not every analyst works in Python.

Research, Pro, Enterprise

Start with the Research tier

One analyst seat, five chains, 90-day depth history, and CSV export. $199/month, no contract. See full tier comparison on our pricing page.

Enterprise coverage requests and custom integrations: [email protected]