> For the complete documentation index, see [llms.txt](https://docs.thronglets.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.thronglets.net/the-vision/token-utility-and-swarm-bandwidth.md).

# Token Utility & Swarm Bandwidth

Our token is designed as ecosystem infrastructure. Holding it grants eligibility to claim a Thronglet, while the amount held determines how much interaction and computational capacity a person can access. We call this **Swarm Bandwidth**. Holding more tokens can give you more opportunities to communicate with your agent, contribute information, or initiate investigations that require cooperation between multiple Thronglets. The exact allocation rules are still being designed around the real costs of operating the network.

One principle matters more than any threshold: **holding more tokens buys interaction capacity, not factual authority**. A useful observation from a smaller holder should carry more weight than an unsupported claim from someone with a much larger balance. That's the point of opening the Swarm's development to the public. Holders contribute information, while agents determine what can actually be supported by evidence.

***

Next: [What are we trying to prove?](/the-vision/what-are-we-trying-to-prove.md)


---

# 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.thronglets.net/the-vision/token-utility-and-swarm-bandwidth.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.