Use your own keys
Run the agents on your bench against your own model provider accounts.
The agents on your bench call their models with your keys, on your provider accounts. The samples use the shell variables from Before you start.
- Add your provider keys to your workspace. Every harness Veris runs for you, such as Claude Code, Codex or Pi, can use them.
- If you bring your own agent, add its keys to your bench’s candidate-env, as in Add your agent.
- The simulated user and the grader run on Veris’s keys. Nothing to set.
Add a provider key
You need the member role in your workspace. Each workspace holds one key per provider; saving a second key for a provider replaces the first. Once saved, a key’s value is never shown again.
Console
Open Overview and choose the Provider keys card. In Workspace keys, pick a provider under Add a key, paste the API key, fill any other field the provider asks for, and choose Save key.
Providers
| Provider | provider | api_key | Also send |
|---|---|---|---|
| Anthropic | anthropic | API key | |
| OpenAI | openai | API key | |
| Azure OpenAI | azure | API key | base_url: your endpoint, https://<resource>.openai.azure.com/openai/v1 |
| Amazon Bedrock | bedrock | Bedrock API key | region, such as us-east-1 |
| Claude Platform on AWS | anthropic-aws | Workspace API key, or <access key id>:<secret access key> | region and workspace_id (wrkspc_...) |
| GitHub Copilot | github | Fine-grained personal access token with the Copilot Requests permission | |
| Google Gemini API | google | API key | |
| DeepSeek | deepseek | API key | |
| xAI | xai | API key | |
| Meta Model API | meta | API key | |
| Baseten | baseten | API key | |
| Fireworks AI | fireworks | API key. See Fireworks AI. |
Add a harness candidate
Veris adds harness candidates to your bench: a vendor’s agent such as Claude Code or Codex, or an open-source one such as Pi, Hermes Agent or OpenCode. Save the provider key first, then write to hello@veris.ai with your bench’s id and, for each candidate, the harness, the provider and the model.
Once it is on the bench, run a trial with it.
When the key is used
- The key is read when a trial starts, and the trial keeps that key to its end. A key you replace or remove applies from the next trial.
- A fork brings the bench’s harness candidates, not keys. Trials on your fork run on your workspace’s keys.
- A bench shared with your workspace runs on its owner’s keys, and only in the owner’s workspace.
Remove a key
Console
Open Overview, choose the Provider keys card, and choose Remove beside the key.
Troubleshooting
| What you see | Why | What to do |
|---|---|---|
409 at trial start: workspace has no <provider> API key — add one in workspace settings | A harness candidate needs a provider your workspace has no key for. | Add the key. |
422 <provider> keys need a region or do not take a base_url | The key is missing a field it needs, or has one it doesn’t take. | Send the fields listed for the provider. |
| Attempts fail with the provider’s own authentication or quota error | The key was refused, or its account is out of quota. | Replace the key, or raise the limit with your provider. |