> For the complete documentation index, see [llms.txt](https://docs.fyda.fi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fyda.fi/trade-engine.md).

# Trade Engine

Fyda's Trade Engine lets users create and execute strategies, combining on-chain and off-chain solutions for enhanced accessibility.

Trade Engine architecture consists of following components:

* **Strategy Contracts**: These smart contracts access users' wallets, enable users to create strategies and execute trades.
* **Liquidity Contracts**: Smart contracts that facilitate trade execution by connecting with on-chain liquidity providers and decentralized exchanges (DEXs).
* **On-Chain Price Oracles**: Fyda integrates with on-chain price oracles like Chainlink to fetch historical prices to execute trades and protect against price manipulation.
* **Trading Bots**: These bots are Off-chain systems that monitor prices and trigger trade execution.


---

# 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://docs.fyda.fi/trade-engine.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.