THEEXCHAIN / Liquidity as a Service

Depth changes the moment of execution.

Explore how order size and available sources shape a route.

Editorial illustration of liquidity sources converging
LIQUIDITY AS A SERVICETHEEXCHAIN / LIQUID
OPTIONAL / INTERACTIVE SAMPLEExplore the Liquidity as a Service workflow
INTERACTIVE PREVIEW / LIQUIDITY AS A SERVICE

Liquidity as a Service

Sample data

Preparing the interactive preview…

Local demonstration · no live accounts or transactions
01 / The market question

A quoted price is not
the whole story.

Execution quality depends on how much depth is available at each level, how routes respond to order size and whether sources remain available when market conditions change. TheExChain's liquidity proposition joins market making, order-book management, liquidity-pool access and tailored routing into a single decision framework.

03 / Operating architecture

Three things to connect
before a trade.

01

Liquidity sources

Evaluate venues, pools or market-making relationships against pairs and operating requirements.

02

Routing logic

Consider size, available depth, price, source health and the conditions under which a route changes.

03

Execution oversight

Record outcomes, exceptions and source availability so the team can review quality over time.

04 / Where it matters

Different markets.
Different depth needs.

EXCHANGE MARKETS

Help an order book present and manage depth across the pairs your platform supports.

LARGER ORDERS

Plan how a route responds when size exceeds the best displayed level.

CONTINUOUS OPERATIONS

Monitor source availability and exceptions instead of treating liquidity as a one-time integration.

Field note / Execution quality

A route is only as good as its weakest source.

Displayed depth can disappear before an order reaches the market. Routing rules should account for size, source health, price movement and the conditions that require a pause.

THE DECISIONShow the operator why a route was chosen, changed or rejected.
Operating detail

What needs to be true.

Three decisions to carry into the product and operating model.

  1. 01

    Depth

    Compare available size at the relevant price levels.

  2. 02

    Fallback

    Define when to use another source and when to stop.

  3. 03

    Review

    Preserve the quote, route and final execution for comparison.

Explore an order-size decision

The top available level may be enough. Confirm the quote and source health before routing.

Illustrative decision path · no live data
Questions

Ask about the
whole route.

Does liquidity depend on the asset pair?

Yes. Available depth and execution conditions vary by pair, venue and market conditions.

Can sources be added over time?

The architecture can be designed to accommodate new liquidity connections as the platform evolves.

Why does order size change the route?

Available depth can vary across price levels and sources. A larger order may require a different execution path and additional safeguards.

Is the best quoted price always the best execution?

Not necessarily. Depth, fees, source availability and execution conditions all matter alongside the top visible price.

What should be monitored after launch?

Source health, spread, depth, routing outcomes and exceptions should be reviewable by the operating team.