Source: https://docs.sogni.ai/agents/authentication/

# Agent authentication

## [#](https://docs.sogni.ai/agents/authentication/#connect-an-account)Connect an account

Sign in or create an account at [dashboard.sogni.ai](https://dashboard.sogni.ai/?source=agent-docs), complete the verification shown there, and obtain your API key from the account menu. Return to your installer to finish setup. A pending verification step requires your participation; an agent should wait for you to finish it.

For the CLI, provide the key through the installer prompt or set `SOGNI_API_KEY` through your runtime's secret configuration. For REST, follow the [API authentication reference](https://docs.sogni.ai/api-reference/getting-started/#authentication). Do not put the value in a prompt, URL, source file, screenshot or command saved to shell history.

## [#](https://docs.sogni.ai/agents/authentication/#check-access)Check access

```
sogni-agent doctor --json
```

Check the individual `auth` result. `status: "pass"` means the key was accepted. A warning means access was not verified; overall `success: true` alone is insufficient. A successful authentication check does not guarantee model eligibility or sufficient funds.

## [#](https://docs.sogni.ai/agents/authentication/#account-key-permissions)Account key permissions

The current integration uses an account API key (as of September 2026). Treat it as account access, not a separately scoped grant for a named agent. Do not assume it has an independent expiry or spending allowance. Keep each runtime's stored copy private; replace the key through the dashboard's available account controls if it is exposed, then update your configured runtimes.

Existing API-key access is not permission to charge a saved card. [Fund your account](https://docs.sogni.ai/agents/pricing/) through the supported user flow. Hosted OAuth/device authorization and separately revocable agent grants will need their own documented setup when available.