Settings & API keys

Open Workspace settings from the sidebar (shortcut g s), or jump to a project's keys from its overview.

API keys

Keys authenticate the SDK and the ingest endpoints. They're scoped per project and look like vk_live_....

• Create a key from the API Keys panel. The full secret is shown once, at creation — copy it then.
• After creation it's stored hashed; the dashboard can't reprint it. If you lose it, create a new one.
• Revoke a key to disable it immediately (requests using it get 401). Revoked keys stay listed for audit.

Warning: a truncated key like vk_live_Ok3… shown in a snippet is only the key's prefix (an identifier), not the full secret. Use the key you copied at creation, or create-and-reveal a fresh one from the Connect screen.

Your OpenAI key

Above the per-project API keys, the API Keys panel has one account-level slot: Your OpenAI key.

Add your own OpenAI key here and Veralith runs your judges (Sufficiency, Faithfulness, Completeness) on it. It's set once for your whole account and applies to every project — you don't add it per project.

• Add key → paste an sk-... key. Veralith verifies it with OpenAI before saving, so a typo'd key is rejected on the spot rather than silently failing later.
• It's stored encrypted and is write-only — after saving, the dashboard only ever shows a …last4 hint, never the full key.
• Replace swaps in a new key; Remove clears it. Your existing traces and diagnoses are unaffected either way.

Note: this is different from the vk_live_... keys below it. Those authenticate the SDK so it can send traces; Your OpenAI key is your LLM-provider key that runs the evaluation itself.

Connect snippets

On key creation (and on the first-run Connect screen), Veralith gives you ready-to-paste setup for each surface:

• SDK — pip install veralith, the env var, and the veralith.log(...) line.
• Coding agent (MCP) — a claude mcp add one-liner and a .mcp.json block for Claude Code, plus Cursor and Codex variants.

See Integration for what each does, and Connection status to confirm they're wired up.

One key, one place

Both the SDK and the MCP agent read the same VERALITH_API_KEY. If you set it once as an environment variable and reference ${VERALITH_API_KEY} in your agent config, switching a project's key means changing it in a single place. (Note: your editor reads the real environment, not a .env file — export the variable so both the SDK and the agent pick it up.)