> ## Documentation Index
> Fetch the complete documentation index at: https://docs.anpord.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Connections

> The credentials your evals run with

An eval needs two credentials: one for the harness that does the work, one for the sandbox it works in. Anpord supplies neither — you bring your own accounts, and model and sandbox usage is charged to them.

Add both under **Settings > Connections** before the first run. This applies to the SDK, CLI, and MCP too; there is no way to pass a raw key through the API.

## Add one

Choose **Add connection**, pick the integration, paste the key. Secrets are encrypted on arrival and never shown again.

You need one [harness](/evals/harnesses) and one sandbox — `daytona`, `e2b`, `upstash`, `modal`, `cloudflare`, or `vercel`. Only the ones your run names.

The first connection for an integration becomes its default, and runs use defaults unless you pick otherwise. **Verify** checks a stored credential against the provider without revealing it.

## Personal or shared

Organization connections are usable by everyone. Personal ones are yours alone and take precedence for the same integration, which is how you run against your own account without changing what your team uses.

## When one is missing

```text theme={null}
No credential configured for codex
```

Nothing is charged and no sandbox opens. In the dashboard the run button stays disabled and names what is missing.

## Rotating and removing

**Rotate** replaces the secret in place, keeping the id and default, and makes an `invalid` credential active again.

Removing one leaves past runs readable. Removing a default leaves the integration without one, so set another before the next run.