> For the complete documentation index, see [llms.txt](https://docs.apex.win/apex-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.apex.win/apex-docs/developer-guide/keeper-bot/keeper-bot-guide.md).

# Running your own bot

We have provided two implementations of our keeper bots that are both written in python.

No knowledge of python is required to run the bots, however we would advise a basic understanding of python.

The [APEX KEEPER](https://github.com/perpfutui/APEX-KEEPER) uses brownie to manage the interface with the blockchain. This bot is slightly easier to run

The[ CHRONOS BOT ](https://github.com/perpfutui/chronos_bot)interacts directly with the blockchain using web3py. It has slightly better performance than the APEX KEEPER so we would recommend this bot for those who are serious about running a keeper bot.

Please follow the instructions provided on github to run the bots.

Please note: the bots are provided as-is. We will be able to provide some assistance with troubleshooting.


---

# 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.apex.win/apex-docs/developer-guide/keeper-bot/keeper-bot-guide.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.
