# Key expiration and rotation

Keep credentials current without resetting usage limits.

Source: https://docs.ravenrelay.joshlab.site/key-lifecycle

Agent index: https://docs.ravenrelay.joshlab.site/llms.txt
OpenAPI: https://docs.ravenrelay.joshlab.site/openapi.json

## Manage credentials

API Keys in the dashboard supports an optional expiration date in your local time. Expired keys cannot authorize new requests or queued dispatches. Leave the date empty for no expiration.

Rotate replaces a secret immediately. Save the new secret once and update your server configuration. Rotation preserves the key identity, permissions, expiration and monthly development allowance. Requests using the previous secret are rejected. For an overlap period, create a separate key, deploy it, then revoke the previous key.

> Never put keys in browser code, source control or public logs. Workspace owners, administrators and developers with write access can create, rotate or revoke project keys.