> For the complete documentation index, see [llms.txt](https://eu.support.backpack.exchange/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://eu.support.backpack.exchange/start-here/about-backpack-eu.md).

# About Backpack EU

Trek Labs Europe Ltd dba Backpack EU is a Cyprus-registered entity, authorized and regulated by the Cyprus Securities and Exchange Commission (CySEC) to provide investment services and operate with financial instruments pursuant to MiFID II.

[Backpack EU](https://eu.backpack.exchange/) is the European arm of Backpack Exchange, a globally regulated and forward-thinking cryptocurrency platform. With a strong commitment to rebuilding trust in the digital asset space, Backpack EU has proudly taken on the responsibility of ensuring the safe return of funds to former FTX EU Ltd clients.

Now operating under a MiFIDII regulatory license, Backpack Europe is excited to provide one of the first fully licensed crypto-derivatives exchanges in the EU, including access to regulated perpetual futures and advanced trading products.

[Backpack EU](https://eu.backpack.exchange/) provides services exclusively to clients residing within the European Economic Area (EEA). Please find [here](https://eu.support.backpack.exchange/exchange/account/supported-regions-and-countries.md) the supported regions & countries.


---

# 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://eu.support.backpack.exchange/start-here/about-backpack-eu.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.
