Every API key is bound to a single Outkit profile at creation time. The CLI surfaces the full lifecycle.Documentation Index
Fetch the complete documentation index at: https://docs.outkit.dev/llms.txt
Use this file to discover all available pages before exploring further.
Create
- Creates a new key under the active profile (from
outkit.json). - Shows the plaintext key exactly once — it’s never shown again, never logged, and only the SHA-256 hash lives in our database.
- Offers to append
OUTKIT_API_KEY=…to.env.local(or your project’s env file).
--profile <id> to bind to a different profile without switching the active one:
List
Stats
Rotate
Revoke
401
on the next call. Use -y to skip the confirmation prompt.
Storage rules
- Plaintext keys are shown in your terminal exactly once at creation/rotation. Save them immediately. There is no way to recover a key after the screen scrolls.
- Never commit a key. The CLI’s env-file write helper appends to
.env.local(gitignored by most frameworks). - The CLI never stores a plaintext key on disk.
Next Steps
Use the key in your app
Wire
OUTKIT_API_KEY into your backend proxy.Tail render logs
outkit logs tail streams new render events as they happen.