> ## Documentation Index
> Fetch the complete documentation index at: https://docs.aiohub.org/llms.txt
> Use this file to discover all available pages before exploring further.

# Create an API key

> Create and manage `sk-` API keys for AIOHub API requests.

## Create an API key

<Steps>
  <Step title="Open API key management">
    Open [API key management](https://api.aiohub.org/console/token) and sign in.
  </Step>

  <Step title="Create a new API key">
    Select **Add new API key**, then configure the fields you need:

    | Field        | Meaning                                            |
    | ------------ | -------------------------------------------------- |
    | Name         | A label that helps you identify the client or task |
    | Group        | One or more groups the API key can use             |
    | Quota        | Optional usage cap for this API key                |
    | Expiration   | Optional expiration time                           |
    | Model limits | Optional allowlist for specific models             |
    | IP limits    | Optional allowlist for source IP addresses         |
  </Step>

  <Step title="Copy the API key">
    Copy the API key after it is created:

    ```text theme={"system"}
    sk-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
    ```

    <Warning>API keys are sensitive credentials. Store them in local environment variables, a secrets manager, or a trusted backend. Do not commit them to source control.</Warning>
  </Step>
</Steps>

## Groups

An API key can be assigned to multiple groups. If you choose `auto`, AIOHub picks from active groups based on the current routing configuration. See [Groups](/en/account/groups) for the current group snapshot and client-specific guidance.

## Security practices

* Do not share API keys with other people.
* Store API keys in environment variables instead of hardcoding them.
* Use separate API keys for separate tools so you can track usage and set limits independently.
* Rotate API keys periodically.