> For the complete documentation index, see [llms.txt](https://bingo-maker.bingaodobrasil.com.br/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bingo-maker.bingaodobrasil.com.br/getting-started/bingo-maker.md).

# Bingo Maker

Technical Documentation: Bingo Maker

**Bingo Maker** is a robust software component designed to facilitate the creation, management, and execution of bingo games within an online gaming platform. It serves as the core engine that handles the logic, mechanics, and user interactions associated with bingo gameplay. The Bingo Maker is integrated with various APIs to ensure seamless operation and interaction with other system components, such as the Hub and game providers.<br>

The **Bingo Maker** is a critical component of the online bingo gaming ecosystem, providing the necessary tools for operators to create and manage engaging bingo experiences. Its integration with various APIs ensures smooth operations, real-time interactions, and comprehensive reporting, making it an indispensable tool for any online gaming platform that offers bingo games.

{% content-ref url="/pages/Zvukm7MAGL6ooitMTmpY" %}
[Getting Started](/getting-started/bingo-maker.md)
{% endcontent-ref %}


---

# 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://bingo-maker.bingaodobrasil.com.br/getting-started/bingo-maker.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.