> 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/permisionless-utilisation-of-virtual-agents.md).

# Permisionless Utilisation of VIRTUAL Agents

The VIRTUAL ecosystem offers any applications or users the ability to subscribe to and utilize a variety of VIRTUAL agents based on their specific requirements. This process is permissionless and designed for maximum flexibility.

The subscription and integration procedure is streamlined for ease of access and is readily available through the Protocol App.

**Accessing Virtuals via Protocol SDKs**:

* App developers must create an account with the Protocol App. 
* Within this account, an App application will be generated and a VIRTUAL agent selected. 
* An API Key will be generated for the chosen VIRTUAL agent's usage. 
* If there is a need for another VIRTUAL agent, a new App application should be created.

For Application developers, read [here](broken://pages/CvlpZ8akhN6U9GUWi8Rw).


---

# 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://whitepaper.virtuals.io/about-virtuals-1/the-protocol/permisionless-utilisation-of-virtual-agents.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.