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

# Registrations

Once a collection has been integrated into the Basebrawl protocol, the final step before a Brawler begins their journey is to execute registration for a specific TokenId. Registration populates a Brawler's initial manoeuvre set and statistics, allowing access to the queue system and arenas.

The protocol provides the ability for governance to define a cost for registration, denominated in any ERC20 token. The amount and token chosen for registration is configurable on a per collection basis, allowing communities with their own tokens to negotiate with the BaseBrawl community on payment terms - providing a pathway for adding additional utility to their ecosystem by integrating with the BaseBrawl protocol.

{% hint style="info" %}
Fees collected from Brawler registrations accrue to the protocol fee collector. As governance becomes decentralized and handed to the community, the BaseBrawl DAO will govern the use of this treasury for the betterment of the protocol.
{% endhint %}


---

# 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:

```
GET https://basebrawl.gitbook.io/basebrawl/registrations.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.