> For the complete documentation index, see [llms.txt](https://docs.ai.neevcloud.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ai.neevcloud.com/getting-started/create-api-key.md).

# API Key

API keys let you authenticate requests and connect your applications to NeevCloud resources.

## Create an API Key

1. Log in to the [NeevCloud Console](https://console.ai.neevcloud.com/).

![](https://1980728309-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSqquJG2zKVZ5l1Sd5aQy%2Fuploads%2Fgit-blob-a29fab745187725535c7bbfe8fa181e9cd34075e%2Fone.png?alt=media)

2. Under **Account**, select **API Keys**.
3. Click **Create New API Key**.
4. Enter a name for your API key.
5. Select the **Resource Type** you want to use the key with.

![](https://1980728309-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSqquJG2zKVZ5l1Sd5aQy%2Fuploads%2Fgit-blob-e36fbb385dbb4b56eb5a667da1e5c85a95ac783b%2Fthree.png?alt=media)

6. Click **Create**.
7. Copy your API key and store it securely.

> **Important:** Keep your API key private. Do not share it or commit it to public repositories.

You can now use the API key in the relevant NeevCloud tutorials and workflows.


---

# 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://docs.ai.neevcloud.com/getting-started/create-api-key.md?ask=<question>&goal=<user_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.