> 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/2.-background-and-market-context.md).

# 2.  Background and Market Context

In recent years, proprietary trading firms, commonly known as "prop firms," have gained momentum in the financial markets. The advantage for traders is the opportunity to earn significant profits without risking their own funds, while the firm takes a share of the profits as compensation. As global markets become more interconnected and digitalized, the demand for efficient, technology-driven trading solutions has surged, providing a fertile ground for prop firms.

EOSI Finance aims to innovate within this thriving sector by incorporating cutting-edge technology and data-driven strategies. EOSI Finance's approach is to leverage these technological advancements to offer a robust and competitive platform for traders worldwide, addressing the growing need for agile and scalable trading solutions.


---

# 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/2.-background-and-market-context.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.
