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

# $CBROKE

## About the token

**$CBROKE** is the token at the beginning of the BROKE CEO ecosystem.<br>

<figure><img src="https://3912587727-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FaCkwEOotyUZP6FOZ4a0Y%2Fuploads%2FRGvte9Bep6YIrYpwYLh9%2FCOIN%20CBROKE.png?alt=media&amp;token=950f07c0-5b58-4143-b2c2-6e707f6cb122" alt="" width="188"><figcaption></figcaption></figure>

The project is currently developing its launch and brand infrastructure. The launch blockchain has **not been finalized** and will be announced once confirmed.

## Current direction

The planned token concept is focused on a community-driven launch and a long-term ecosystem around BROKE CEO.

The current project plan includes:

* **Ticker:** $CBROKE
* **Planned total supply:** 1,000,000,000
* **Team allocation:** 0% planned
* **Private sale:** 0% planned
* **VC allocation:** 0% planned
* **Reserved team tokens:** 0% planned

These are current plans and should be treated as subject to final confirmation before launch.

## Utility

$CBROKE is planned to become increasingly integrated into the BROKE CEO ecosystem, including potential use in:

* Selected BROKE Store items
* NFT-related mechanics
* Future ecosystem interactions
* Potential evolution mechanics
* Potential burn and treasury mechanics

Specific percentages, requirements, and mechanics will be announced when finalized.

## Network

**TBA**

The launch network has not been finalized.


---

# 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://broke-ceo.gitbook.io/broke-ceo-docs/usdcbroke.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.