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

# Background

<figure><img src="/files/GqHchSa5ciurk3RkOPO9" alt=""><figcaption></figcaption></figure>

The cryptocurrency market has experienced explosive growth over the past decade, attracting a diverse range of participants from individual investors to large-scale enterprises. However, with this growth comes increased complexity and the need to efficiently manage various crypto-related tasks. From trading and portfolio management to community engagement and market analysis, the demands on crypto enthusiasts and developers are substantial.

Traditional tools for managing these tasks often require significant technical expertise and can be fragmented across different platforms. This fragmentation not only increases the complexity but also raises concerns about security and reliability. There is a clear need for a unified platform that simplifies crypto automation, ensuring that users can efficiently manage their activities with the hassle of juggling multiple tools.


---

# 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://botify-cloud.gitbook.io/whitepaper/introduction/background.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.