Set your Anthropic key
- Select the organization that will own the evals.
- Open Settings > Environment and choose Add variable.
- Enter
ANTHROPIC_API_KEYwith your Anthropic API key and choose Everyone in the organization, so CLI, SDK and CI batches can use it. - Save it.
sphynx env set ANTHROPIC_API_KEY does the same. It needs an API key with credentials:write, as the CLI guide describes.
The key stays in Sphynx. A local Claude login or Claude subscription does not authenticate these trials: Sphynx uses Claude Code’s bare mode, which requires API credentials.
Create a Sphynx API key with evals:read and evals:write in the same organization and set it as SPHYNX_API_KEY in your shell or CI secrets. Your eval file and GitHub workflow hold no Anthropic key. Hosted E2B sandboxes need no key of their own.
Check one trial
Installsphynx-sh, then create claude.eval.ts:
Compare models
Keep the cases and add variants:If setup fails
- Set ANTHROPIC_API_KEY in Settings > Environment to run claude: check the organization, and that the key is set for everyone in it.
- Authentication rejected: set
ANTHROPIC_API_KEYagain with a working key. - Model unavailable: check the exact ID and your account’s access.
- Works locally but fails in CI: an API key uses the organization’s values, not your personal ones or your local login.