> For the complete documentation index, see [llms.txt](https://arbydex.gitbook.io/arbydex/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://arbydex.gitbook.io/arbydex/arbydex-technology/market-discovery.md).

# Market Discovery

### Finding Opportunities Across Markets

The first stage of the ARBYDEX engine is Market Discovery.

The system continuously scans supported decentralized markets to identify potential price differences between liquidity venues.

#### Discovery Process

{% code expandable="true" %}

```
Market Data
↓
Price Comparison
↓
Opportunity Detection
↓
Candidate Opportunity
```

{% endcode %}

The discovery layer evaluates market data and searches for price discrepancies that may create an arbitrage opportunity.

#### What The Engine Looks For

• Price differences\
• Trading pair availability\
• Market activity\
• Liquidity availability\
• DEX conditions\
• Potential execution routes

Market Discovery does not automatically mean execution.

Every detected opportunity moves through additional analysis layers before the engine can determine whether it qualifies.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://arbydex.gitbook.io/arbydex/arbydex-technology/market-discovery.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.