> For the complete documentation index, see [llms.txt](https://eosi-finance-1.gitbook.io/eosi-finance-documentations/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://eosi-finance-1.gitbook.io/eosi-finance-documentations/eosi-finance/5.-architecture-of-the-eosi-finance-ecosystem/5.5-integration-with-third-party-protocols.md).

# 5.5  Integration with Third‑Party Protocols

<mark style="color:$primary;">**EOSI Finance**</mark> integrates with a variety of **decentralised exchanges (DEXs), DEX aggregators, bridges and other DeFi APIs** to source liquidity and execute trades. For example, when a pro trader places a trade, the underlying smart contract may route orders through Hyperliquid, Uniswap or another DEX aggregator to obtain the best available price. Similarly, cross‑chain trades may involve bridging assets via third‑party bridge protocols.&#x20;

**These integrations are governed by the terms of service of the respective third‑party providers**, and users interacting with <mark style="color:$primary;">**EOSI Finance**</mark> implicitly accept those terms. While we endeavour to select reputable partners, <mark style="color:$primary;">EOSI Finance</mark> does not control or guarantee the performance of these external protocols.

Where a third‑party protocol requires identity verification, AML or KYC checks, users must complete those processes directly with the third‑party provider. <mark style="color:$primary;">EOSI Finance</mark> will not collect or store KYC data unless required by law or governance proposals.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://eosi-finance-1.gitbook.io/eosi-finance-documentations/eosi-finance/5.-architecture-of-the-eosi-finance-ecosystem/5.5-integration-with-third-party-protocols.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.