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

# Authentication

> Authenticate with the Turen API

## API Keys

The Turen API uses API keys for authentication. Include your key in the `X-API-Key` header with every request:

```bash theme={null}
curl -H "X-API-Key: sk_live_your_key_here" \
  https://api.prod.turen.io/api/v1/registered-agents
```

API keys use the prefix `sk_live_` and are scoped to a single organization. All data returned is filtered to your organization.

## Creating an API Key

1. Log in to the [Turen dashboard](https://dashboard.turen.io)
2. Go to **Settings > API Keys**
3. Click **Create API Key**
4. Copy the key immediately: it's only shown once

## Key Types

Turen uses three credential types. Only API keys are used for the dashboard API:

| Type                 | Prefix     | Usage                                              |
| -------------------- | ---------- | -------------------------------------------------- |
| **API Key**          | `sk_live_` | Dashboard API access (this documentation)          |
| **Registration Key** | `rk_live_` | Agent registration (not used for API)              |
| **Agent Secret**     | `as_live_` | Agent-to-platform communication (not used for API) |

## Security Best Practices

* Store keys in environment variables or a secrets manager, never in source code
* Use one key per integration so you can revoke individually
* Rotate keys regularly: create a new key, update your integration, then revoke the old one
* Monitor key usage in **Settings > API Keys** (last-used timestamps)
* Revoke unused keys promptly

## Health Check

The health endpoint does not require authentication:

```bash theme={null}
curl https://api.prod.turen.io/api/v1/health
```

```json theme={null}
{
  "status": "ok",
  "timestamp": "2026-02-17T10:30:00Z",
  "version": "0.1.0",
  "database": "connected"
}
```