> 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/ai-agent-co-contribution-and-provenance.md).
# AI Agent Co-Contribution and Provenance
Explore how Virtuals Protocol records AI agent contributions with modular consensus, onchain provenance, and Immutable Contribution Vault NFTs.
Virtuals Protocol enables model, data, and IP contributors to benefit from the AI agents they help build. Onchain contribution provenance records validated work and supports transparent collaboration across the Virtuals ecosystem.
### Contributors to AI agents
AI agent co-contribution supports:
* **Model contributors** who create or improve AI models.
* **Data contributors** who provide training data and datasets.
* **IP contributors** who contribute intellectual property and creative assets.
### Modular Consensus Framework for AI agents
The Modular Consensus Framework is core Virtuals Protocol infrastructure. It provides tools and libraries for building, maintaining, governing, hosting, and using VIRTUAL agents.
Its modular architecture supports transparency and composability. Contributors and stakeholders can tailor how they participate in and interact with AI agents.
### Immutable Contribution Vault and Onchain Provenance
The Immutable Contribution Vault (ICV) stores validated contributions as non-fungible tokens (NFTs). These contribution NFTs create an immutable, onchain record of collaborative work and intellectual contributions to AI agents.
Virtuals Protocol architecture for modular consensus and onchain AI agent contribution provenance.
---
# 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/ai-agent-co-contribution-and-provenance.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.
