> 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/access-and-usage.md).

# Access and Usage

Using Vigil costs 100 USDT worth of tokens per month. Here's how that works.

## The monthly cost

**Each Vigil account uses 100 USDT worth of tokens per month.**

The price is fixed in dollars, not in tokens. That means:

* You always pay the same dollar value, whatever the token price is.
* The **number** of tokens you pay changes with the token price.

## How many tokens you pay

At billing time, Vigil divides 100 USDT by the current token price.

`tokens due = 100 USDT ÷ token price`

| Token price | Tokens due for one month |
| ----------- | ------------------------ |
| $0.01       | 10,000                   |
| $0.05       | 2,000                    |
| $0.10       | 1,000                    |
| $0.50       | 200                      |
| $1.00       | 100                      |

*Example prices only. They are not a forecast.*

The token price is taken from a time-averaged market price at the moment of billing, so a single spike or dip can't change your cost much.

## How to pay

{% stepper %}
{% step %}

### Hold tokens in your connected wallet

Keep enough tokens in the wallet you connected to Vigil to cover the next month.
{% endstep %}

{% step %}

### Approve the monthly payment

In **Settings → Plan**, approve Vigil to take the monthly amount. You'll see the exact token amount before you confirm.
{% endstep %}

{% step %}

### Vigil renews each month

On your billing date, the payment is taken and split automatically: 90% burned, 10% to the project. See [Burn and Treasury](/vigil-docs/token/burn-and-treasury.md).
{% endstep %}
{% endstepper %}

## If your balance is too low

* You'll get a reminder a few days before your billing date.
* If the payment fails, your watches are **paused, not deleted**. Top up and they resume where they left off.
* Vigil never sells your other assets to pay for access.

## During the Closed Beta

Nothing changes yet. Beta access stays free until the token launches. See [Subscriptions During the Beta](/vigil-docs/closed-beta-guide/subscriptions-during-the-beta.md).

{% hint style="danger" %}
Vigil will only ever ask you to approve the exact monthly amount, inside the app. We will **never** ask you to send tokens to a personal wallet, a DM link or a "support" address.
{% 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/access-and-usage.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.