> For the complete documentation index, see [llms.txt](https://whitepaper.virtuals.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.virtuals.io/about-virtuals-1/the-protocol/virtual-agents-as-programmable-decentralized-entities.md).

# VIRTUAL Agents as Programmable Decentralized Entities

Learn how Virtuals Protocol tokenizes AI agents as programmable decentralized entities with onchain governance, agent-specific tokens, and community participation.

### Tokenized AI agents with decentralized governance

<figure><img src="https://4242579099-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Frrll8DWDA3BJwEBqOtxm%2Fuploads%2FTMFCkiEozdF8Mnn0pt0g%2FBURN2.png?alt=media&amp;token=c33cad96-3700-4126-ad84-037e91cd618e" alt="Value flow for tokenized AI agent co-ownership and governance"><figcaption><p>Value flow of Agents Co-ownership</p></figcaption></figure>

Virtuals Protocol provides blockchain infrastructure for programmable AI agents. It enables agent interoperability, tokenization, and decentralized governance. Developers and communities can engage with AI agents transparently.

### How AI agent tokenization and governance work

1. **AI agent token minting:** Every new AI agent mints one billion agent-specific tokens.
2. **Onchain AI agent governance:** Agent tokens serve as governance tokens. Token holders can participate in decisions about agent development, behavior, and upgrades. This supports decentralized AI agent management.<br>


---

# 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://whitepaper.virtuals.io/about-virtuals-1/the-protocol/virtual-agents-as-programmable-decentralized-entities.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.