> For the complete documentation index, see [llms.txt](https://docs.uncaged.bet/uncaged/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.uncaged.bet/uncaged/overview/what-is-uncaged.md).

# What is Uncaged?

Introducing Uncaged, the AI-powered Telegram bot set to augment the betting industry.\
\
We want to offer the best experience to sports betting users through a combination of solutions:

* [Telegram](/uncaged/tech/telegram.md)-based Bot, with a premium on accessibility and UI/UX experience, making sure even not-crypto savvy users can enjoy our platform.
* [AI-enhaced prediction](/uncaged/tech/prediction-model.md), through an ever-evolving and fine-tuned model, with the added possibility of onboarding new "predictors" while expanding to any sport.
* [Account abstraction](/uncaged/tech/account-abstraction.md), offering everyone a layer of safety, and abstracting the need for chain-specific gas through our integrations.

In the earliest stages, we will focus on MMA matches, but... we aim to become more than just a betting bot, expanding to new sports, PVP minigames, and tailored sports datasets.<br>

This documentation will go into detail on how the platform works from both a technical and practical perspective, alongside information on the token and rev model.


---

# 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://docs.uncaged.bet/uncaged/overview/what-is-uncaged.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.