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

# BetAI — Introduction

## Overview

We're an AI-Driven Bets insight platform, aimed at the general public, with the purpose of serving as analytical help of matches on different sports.\
\
Our idea is pretty straightforward — You bet, our AI provides the likelihoods — of anything you want to know.\
\
This will help you make informed decisions, although remember, nothing ever given by an inanimate product is financial advice.\
\
The evaluations we provide should be used as a means of information, a needed data-source to not miss on any details, saving up both your time looking for stats — and thinking them through by yourself — since we do not only provide the data, but also our own assessment of it!\
\
Welcome to BetAI.


---

# 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://betai-1.gitbook.io/betai-technical-paper/betai-introduction.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.