> For the complete documentation index, see [llms.txt](https://docs.reveald.com/technical-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.reveald.com/technical-documentation/data-sources/vicarious-vrx/create-an-api-key-in-vicarious-vrx.md).
# Create an API key in Vicarious vRx
1. Log into Vicarious vRx console with a user that has "Owner" permission. This permissions is required to access the API management and functionality pages.
2. Navigate to Settings -> Select the "api" tag -> Select "Create Integration" to create a new key
To view existing API keys, Navigate to Settings -> Installed Integrations -> Select the "api" tab:
3. From the API page, copy the API key to a secure location for upload to the Epiphany Intelligence Platform Portal.
* Note: API keys are valid until revoked (No expiration date)
---
# 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://docs.reveald.com/technical-documentation/data-sources/vicarious-vrx/create-an-api-key-in-vicarious-vrx.md?ask=&goal=
```
`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.