Skip to main content
Open Settings → API to manage the Entelligence API key used by clients such as the CLI and MCP.

​
Current controls

A configured key can show:
  • A masked value
  • Created date
  • Copy
  • Rotate Key
  • Delete Key
When no key exists, the page provides Create Key. Creation, rotation, and deletion take effect from the current screen; inventory clients before using them.

​
Create and store a key

  1. Select Create Key.
  2. Copy the value when it is displayed.
  3. Store it in an approved secret manager.
  4. Record the owner and consuming workload.
  5. Configure the intended CLI, MCP client, CI job, or automation.
  6. Run a read-only authentication test.
For environments that support it, provide the value through the ENTELLIGENCE_API_KEY environment variable. Do not commit the key to source control or place it in documentation.

​
Rotate without downtime

  1. Inventory every CLI, MCP, CI, and automation consumer.
  2. Schedule a change window.
  3. Rotate the key.
  4. Update every consumer.
  5. Verify each client.
  6. Remove old secret copies.
  7. Confirm that the previous value no longer authenticates.
Deleting the key stops applications using it. Do not rotate or delete until all dependents are known and a recovery path is ready.

​
Security limits to confirm

The current screen does not establish per-key scopes, expiry, ownership metadata, last-used timestamps, or a rotation grace period. If your control framework requires those properties, confirm availability for your Entelligence deployment before documenting them as enforced controls.

​
Next step

Configure MCP or install the CLI.