> For the complete documentation index, see [llms.txt](https://docs.usd.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.usd.ai/governance/chip.md).
# CHIP
CHIP is the governance token of USD.AI. CHIP holders vote on protocol changes, collateral types, and core risk parameters.
## Governance
CHIP Holders use CHIP to vote on the rules that determine how the protocol operates, what collateral is accepted, how loans are priced, and how the system evolves over time.
Core parameters of the protocol are subject to CHIP governance, making token holders collectively responsible for the integrity and direction of the system. To participate in governance, visit
{% hint style="info" %}
For supply, allocation, and vesting details, view [tokenomics](/governance/tokenomics.md).
{% endhint %}
## Staking Module
Staking of CHIP is currently not in use for any protocol functions. You can unstake any previously staked CHIP here:
### Legal Disclaimer
CHIP does not represent equity, ownership, or a claim on protocol assets. Holding or staking CHIP does not constitute an investment in the protocol. CHIP functionality is constrained to on-chain functions defined by smart contracts. Nothing on this page constitutes investment advice.
---
# 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.usd.ai/governance/chip.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.