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

# Token Overview

Vigil will introduce a token that powers access to the agent. Here's the plan.

{% hint style="info" %}
**Coming after the Beta.** The Vigil token has not launched yet. There is no official token today, and nothing is for sale. Any token, contract address or presale claiming to be Vigil's before we announce it on our [official channels](/vigil-docs/community-and-links/community-and-links.md) is not from us.
{% endhint %}

## Why a token

Vigil is a product people pay for every month. The token turns that monthly usage into something simple and transparent:

* **One way to pay.** Access to Vigil is paid in the token.
* **Usage-driven burn.** Most of every payment is permanently destroyed, not kept.
* **Funds for building.** A small, fixed share goes to the project so Vigil can keep running and improving.

## How it works in one picture

| Step         | What happens                                                        |
| ------------ | ------------------------------------------------------------------- |
| 1. Use Vigil | Each account uses **100 USDT worth** of tokens per month            |
| 2. Split     | Every payment is split automatically: **90%** and **10%**           |
| 3. Burn      | **90%** is sent to a burn address and removed from supply forever   |
| 4. Build     | **10%** goes to the project treasury for development and operations |

## At a glance

| Item                | Detail                                                     |
| ------------------- | ---------------------------------------------------------- |
| Name / ticker       | TBA                                                        |
| Chain               | TBA                                                        |
| Monthly access cost | 100 USDT worth of tokens                                   |
| Burn share          | 90% of all tokens received                                 |
| Project share       | 10% of all tokens received                                 |
| Launch              | After the Closed Beta, announced on official channels only |

## Read next

* [Access and Usage](/vigil-docs/token/access-and-usage.md) — how the monthly cost is calculated and paid
* [Burn and Treasury](/vigil-docs/token/burn-and-treasury.md) — where every token goes, and how you can verify it
* [Token FAQ](/vigil-docs/token/token-faq.md) — common questions

{% hint style="warning" %}
The token is designed as a way to access and pay for Vigil. It is not an investment product, and nothing in these docs is a promise of price, profit or return. See [Beta Disclaimer](/vigil-docs/community-and-links/beta-disclaimer.md).
{% 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://vigil-1.gitbook.io/vigil-docs/token/token-overview.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.