# Apex

<figure><img src="/files/fHWrIKiHOH59Sd0ktosK" alt=""><figcaption></figcaption></figure>

### In Closed Beta

An intent-driven intelligence layer that converts natural-language instructions into fully orchestrated trading and yield-generation strategies. Using AI inference and quantitative modeling, Apex interprets user objectives (“rebalance into stables when volatility spikes,” “rotate 20% into ETH if it breaks above support,” “build a conservative yield basket with weekly auto-compounding,” etc.) and automatically constructs strategies that are both executable and backtestable. This removes the need for manual configuration and allows users to describe what they want, rather than how to implement it.

Once a strategy is generated, Apex provides tools for refining, simulating, and validating the approach before committing it on-chain. Users can iterate on parameters, compare variations, and examine expected performance under different market scenarios. A suite of [advanced Indicators](/sherpa-trade-automation/strategy-lab/order-conditions-triggers.md) can be injtently woven together for form confluence driven on-chain outcomes. &#x20;

After deployment, Apex will handle ongoing orchestration, seamlessly interfacing with Sherpa’s execution and automation layers while preserving full user sovereignty. It is the highest-level abstraction within the Sherpa ecosystem—an “everything aggregator” that turns intent into structured, actionable strategy design.

Whether you're asking Apex to 'build a conservative DCA into ETH that pauses during high volatility' or simply stating 'I want crypto exposure without getting rekt,' Apex translates abstract intentions into actionable strategies—identifying suitable assets, entry conditions, risk parameters, and yield opportunities. It's a meta-aggregator that searches across execution venues, yield protocols, and market conditions to deliver tailored options that match your goals and risk tolerance."


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.sherpa.trade/sherpa-trade-automation/apex.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.