> For the complete documentation index, see [llms.txt](https://ticketking.xyz/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ticketking.xyz/docs/it/comandi-del-bot/vote.md).

# /vote

## Comando di voto

### Panoramica

Il `/vote` il comando mostra il link di top.gg per votare Ticket King e quanti voti hai.

### Utilizzo

```
/vote
```

### Descrizione

* **Link per votare**: Mostra il link di top.gg dove voti per Ticket King.
* **I tuoi voti**: Mostra il tuo numero attuale di voti. Ogni voto può essere riscattato per tempo Premium con `/redeem`.

### Quando usarlo

* Quando vuoi votare per Ticket King.
* Quando vuoi controllare quanti voti hai prima di riscattarli.

### Permessi

* Chiunque può usare questo comando.

### Esempio

```
/vote
```

Mostra il link di voto di top.gg e il tuo attuale numero di voti.


---

# 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://ticketking.xyz/docs/it/comandi-del-bot/vote.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.
