Skip to content
engineer9 docs

Bring your own key

You can run engineer9 on your own Anthropic API key, so model usage is billed to your account and runs under your own key’s terms. It’s opt-in. If you don’t provide a key, engineer9 uses the shared key and nothing changes.

How it works

Section titled “How it works”

When you provide an Anthropic API key for your workspace, engineer9:

  1. Validates the key against Anthropic before saving it, so a bad key fails fast instead of producing a broken agent later.
  2. Stores it encrypted at rest (AES-256-GCM). It’s never shown again, only referenced by name.
  3. Uses it for your agent’s model calls from then on.

If no key is provided, engineer9 falls back to the shared key. Nothing breaks, and BYOK stays opt-in.

Setting your key

Section titled “Setting your key”

Your key is configured when your workspace is set up. To add or rotate a key, reach out to the team and it’s applied for your agent.

Data control

Section titled “Data control”

Bringing your own key keeps model usage under your account. Your team’s Memory, the knowledge engineer9 builds, stays within your workspace’s isolated environment (see Isolation & sandbox).

Section titled “Related”