> For the complete documentation index, see [llms.txt](https://docs.ox.security/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ox.security/vibesec/installing-vibesec/creating-new-vibesec-tokens.md).

# Creating New VibeSec Tokens

Before you install VibeSec, you need to create an integration key.

**To create a new integration key:**

1. From the left pane of the **OX dashboard**, select **Settings > API Key Settings**.
2. In the **API Key Settings** window, select **CREATE API KEY**.

<figure><img src="/files/COhaTMxqMhmEB5w0ZqDW" alt="" width="563"><figcaption></figcaption></figure>

1. In the **Create API Key** box set the following:

| Parameter                                      | Description                                                            |
| ---------------------------------------------- | ---------------------------------------------------------------------- |
| **API Key Name**                               | A descriptive name for the API key to identify its purpose MCP key 1   |
| **API Key Type**                               | Select **MCP Integration**                                             |
| [**Assign role**](/admin-settings/roles.md)    | Select **Developer**                                                   |
| [**Assign scopes**](/admin-settings/scopes.md) | Select **Entire organization**                                         |
| **Expiration Date**                            | The date and time when the API key will expire and no longer be valid. |

4. Copy the **API Key Secret** and save the key in a safe location. This is the only time when you can see and copy the actual key.
5. Select **CLOSE**. The new key appears in the **API Key Settings** page.


---

# 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.ox.security/vibesec/installing-vibesec/creating-new-vibesec-tokens.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.