Skip to main content
Two independent controls bound how long a key lives and how hard it can be used.

​
Expiry

Set an expiry (in days) when you mint a key. After it lapses:
  • The key is rejected at the door — every request returns unauthorized.
  • It still appears in your key list and audit log so you keep the history of what it did.
Use short expiries for anything you hand to a third party or paste into a shared machine. No expiry (the default) means the key lives until you revoke it.

​
Per-key rate limit

Set a daily call cap per key, separate from your plan’s shared quota. It’s a blast-radius control: a key that should make a handful of audit calls a day can be capped at, say, 200/day, so a runaway script or a leaked key can’t burn your whole quota.
  • The counter resets daily.
  • When a key exceeds its cap, further calls are refused and logged as denied (reason: rate limit) until the reset.
  • Leave it empty for “no per-key cap” — the key still draws on the shared plan quota.

​
How it relates to plan quota

A call must pass both the per-key cap and the workspace quota. The per-key cap can only ever make a key more restrictive than the plan, never less.

Audit what keys actually did

Per-key and org-wide activity.