> For the complete documentation index, see [llms.txt](https://docs.kiiglobal.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kiiglobal.io/docs/validate-the-network/delegator-information/choosing-a-validator.md).
# Choosing a validator
Choosing a validator requires due diligence.
In order to choose their validators, delegators have access to a range of information directly in the Kii block explorer, where all the validators in the active set will be shown.
* **Validator's moniker:** Name of the validator candidate.
* **Validator's description**: Description provided by the validator operator.
* **Validator's website**: Link to the validator's website.
* **Initial commission rate**: The commission rate on revenue charged to any delegator by the validator (see below for more detail).
* **Commission max change rate**: The maximum daily increase of the validator's commission. This parameter cannot be changed by the validator operator.
* **Maximum commission**: The maximum commission rate this validator candidate can charge. This parameter cannot be changed by the validator operator.
* **Validator self-bond amount**: A validator with a high amount of self-delegated KIIs has more skin-in-the-game than a validator with a low amount.
This information can be found at [app.kiiglobal.io](https://app.kiiglobal.io/)
Example of Staking page
Example of validator profile
---
# 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.kiiglobal.io/docs/validate-the-network/delegator-information/choosing-a-validator.md?ask=&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.
