Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.useveil.co/llms.txt

Use this file to discover all available pages before exploring further.

API keys are managed from Settings → API Keys in the dashboard. Every key is pinned to the mode it was created in — a key minted in sandbox only works against sandbox; a key minted in production only works against production.

​
Creating a live key

Switch the dashboard to Production, then open Settings and click Create new key. The key you create inherits whichever mode the dashboard is currently in — sandbox in sandbox, production in production. Give the key a descriptive name and confirm. If your live identity check is still being reviewed when you click Create, the page shows an inline alert and offers to resume the Go-Live flow without leaving Settings.
Veil shows the full key secret exactly once, immediately after creation. Copy it and store it somewhere safe — you cannot retrieve it again. If you lose it, revoke the key and create a new one.

​
Key details

Each key has a name you choose, a creation date, and a last-used timestamp. The list in Settings shows all keys for the active mode. Switching the dashboard to Sandbox shows only sandbox keys; switching to Production shows only production keys.

​
Rotating a key

There is no in-place rotation. To rotate a key: create a new key, update your integration to use the new secret, then revoke the old key. Revocation is immediate — any call using the revoked secret receives an authentication error right away.

​
Why keys are mode-pinned

A key minted in production can only ever operate in production. This prevents accidental live offramps from a test environment and makes it straightforward to audit which environment each key belongs to. See Sandbox vs. production for the broader isolation model.

​
See also