> For the complete documentation index, see [llms.txt](https://nova-ai-builder.gitbook.io/nova-builders-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://nova-ai-builder.gitbook.io/nova-builders-docs/mission-statement.md).

# Mission Statement

*The Context Layer for Autonomous Intelligence*

Nova AI introduces a transformative approach to autonomous intelligence — agents that are not isolated algorithms but integrated, context-aware systems operating across a decentralized network. Built on the foundational **Model Context Protocol (MCP)**, Nova connects AI agents to tools, data, and infrastructure in a secure and composable manner. At the heart of this ecosystem is the $NOVA token, enabling incentive-aligned participation and permissioned access within a decentralized AI runtime.

***

<figure><img src="/files/YV982eeMfzvZ5VlJ5Fax" alt=""><figcaption></figcaption></figure>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://nova-ai-builder.gitbook.io/nova-builders-docs/mission-statement.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.