API keys
How deployments, workspaces, and local development get LLM Gateway credentials.
Deployments and workspaces
You do not create gateway keys by hand. Crucible issues a separate key for each full deployment, lite deployment, and workspace, and sets LLM_GATEWAY_API_KEY and LLM_GATEWAY_ENDPOINT in its backend environment before the runtime starts. The key is a backend secret, so it never reaches frontend code.
Local development
Open the project in Crucible, choose Work locally, and copy the listed backend file's values into the matching file on your machine. That file includes LLM_GATEWAY_API_KEY and LLM_GATEWAY_ENDPOINT. See Work locally for the full setup.
The llm_gateway standard integration mints each key through the gateway's management API when Crucible provisions a target: a full deployment, a lite deployment or workspace, or one person's local-development access. Each key is scoped to that target, so Crucible can revoke it without touching the others.