> For the complete documentation index, see [llms.txt](https://anyint.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://anyint.gitbook.io/docs/authentication-and-keys/overview.md).

# overview

AnyInt relies on API keys, but the lifecycle and control model vary by product surface. Personal integrations, subscription-backed access, and enterprise team keys all behave slightly differently.

## Key types in practice

| Key type                  | Best for                                        | Typical owner                    |
| ------------------------- | ----------------------------------------------- | -------------------------------- |
| Personal or basic API key | individual development and simple integrations  | one user                         |
| Subscription-backed key   | plan or custom subscription usage               | one account or environment       |
| Team key                  | project, environment, or department-level usage | an organization or project owner |

## Header styles you will see

Different route families expect different auth headers:

```http
Authorization: Bearer <ANYINT_API_KEY>
```

or

```http
x-api-key: <ANYINT_API_KEY>
```

Anthropic-compatible routes also require:

```http
anthropic-version: 2023-06-01
```

## Key lifecycle basics

1. create the key in the dashboard or through the subscription flow
2. show the plain key once
3. store only the masked prefix in UI and the secret in your vault
4. rotate the key when ownership or environment changes
5. revoke the old key immediately if exposure is suspected

## Recommended reading order

* [API Keys](broken://pages/d0b88475fc3f2770f825cfce22c2f402448fd5ce)
* [BYOK](/docs/authentication-and-keys/byok.md)
* [Team Keys](/docs/authentication-and-keys/team-keys.md)