Key Format
Registration keys use the prefixrk_live_ followed by a random string:
Creating a Registration Key
Registration keys are managed separately from API keys. Navigate to Devices > Settings (/agent-control/settings).
Click Create Registration Key
Fill in the key details:
| Field | Required | Description |
|---|---|---|
| Name | Yes | A descriptive name for the key (e.g., “Engineering Team Q1”) |
| Description | No | Additional context about the key’s purpose |
| Max Registrations | No | How many machines can use this key (leave empty for unlimited) |
| Expires In | No | Key expiration: 7 days, 30 days, 90 days, 1 year, or Never |
Registration keys are managed at Devices > Settings (
/agent-control/settings), not in Org Settings > API Keys. They are a separate concept from dashboard API keys.How Registration Works
When a developer installs the Turen agent with a registration key:- The agent generates a unique machine fingerprint
- It sends the fingerprint and registration key to the Turen API
- The API validates the key, creates an agent record, and returns a permanent agent secret (
as_live_) - The key’s usage count is incremented
- The agent stores the agent secret securely for future authentication
Key Properties
| Property | Detail |
|---|---|
| Configurable usage | Set max registrations per key, or allow unlimited |
| Expirable | Keys can be configured to expire after a set period |
| Revocable | Keys can be revoked at any time to prevent further registrations |
| Auditable | Key creation and usage is logged |
Managing Keys
From Devices > Settings (/agent-control/settings), you can:
- View all keys — See key name, description, usage count (current / max), and expiration status
- Revoke a key — Prevent any further registrations with this key
- Delete a key — Permanently remove a revoked key