Depth is execution infrastructure for Base

Most onchain execution systems still rely on shallow signals like TVL, recent volume, and venue reputation when deciding how to interact with liquidity. Those signals do not tell a router, treasury system, or agent whether liquidity is actually clear enough to use in execution decisions.

Depth makes the hidden assumptions explicit. It derives public outputs from onchain state and event data on Base, reads supported onchain oracle feeds rather than third-party market-data APIs, and surfaces what was observed, what passed policy, and what remains unmodeled or refused, so systems can act with fewer unknowns.

For each token and pool set, Depth surfaces:

• which pools are structurally supported
• which pools have recent observation coverage
• which pools are eligible under current policy
• which mechanics are modeled, unmodeled, or refused

Depth does not publish a black-box score or a trade recommendation. It applies explicit policy to observed evidence and publishes the resulting qualification state.

Base already has the liquidity, routing complexity, automation surface area, and agent-facing momentum where bad liquidity assumptions change real behavior.

Depth helps more Base systems act onchain by making liquidity qualification clearer before they route, rebalance, or automate.

In practice, that means:

• routers can narrow candidate pools using explicit qualification before applying their own routing and sizing logic
• treasury systems can automate rebalances against clearer liquidity context instead of treating one boolean as a complete decision
• agents can continue operating when evidence is strong and degrade gracefully when it is partial
• teams can integrate one shared qualification layer instead of rebuilding brittle private heuristics

That matters because systems submit more transactions when they can operate with fewer hidden assumptions. Better qualification can make automation more viable, make execution systems more willing to stay onchain, and let more teams build transaction-driving systems on Base without first owning the full policy burden themselves.

A router, treasury system, or agent can use Depth in a direct transaction path:

• fetch the latest token snapshot from the Depth API (/v1/public/tokens/{token}/latest)
• treat pools that passed current policy as candidate surfaces, and fail closed when they did not
• inspect pool-level context and liquidity metrics before selecting a venue
• submit the onchain swap, rebalance, or routing transaction only after the downstream system's own decision rules also pass

Depth sits directly upstream of systems that do execute the transaction. A policy fail can be a no-go signal; a policy pass is only one input into the downstream execution decision.

Depth is built for systems that need to make execution decisions on Base with fewer hidden liquidity assumptions.

• routers and execution engines
• treasury and protocol automation
• agents and bots that act onchain
• Base-native systems that rebalance, route, or manage liquidity programmatically

Depth is useful wherever better liquidity qualification can make an execution system more viable, more automatable, or more willing to operate on Base.

Depth is not differentiated because it has data. Depth is differentiated because it makes hidden liquidity assumptions explicit.

That shows up in product behavior:

• explicit eligibility instead of implied safety
• explicit refusal when evidence is weak
• visible modeling boundaries instead of silent overreach
• pool-level outputs instead of only token-level summaries
• Base-native handling of concentrated liquidity and Aerodrome-specific structure

Depth is delivered through three connected surfaces:

• Depth Oracle — the core product; signed execution context for Base liquidity
• Depth Explorer — the interface for inspecting token and pool-level outputs
• Depth API — the integration surface for systems that want to consume Depth operationally

Depth is live today through the oracle, explorer, and API.

The system already provides:

• live oracle infrastructure
• signed commitments
• public explorer and API surfaces
• explicit policy and spec versioning

That gives Base builders a new way to inspect and integrate explicit liquidity context into real execution systems.