Authentication

Ageneral splits traffic across two HTTPS hosts. Each host accepts different credentials.

Hosts and credentials

Host	Purpose	Typical credential
`https://ageneral.ai`	Console-backed APIs: projects, members, keys, agents	Bearer token from sign-in
`https://models.ageneral.ai`	OpenAI-compatible Models inference	Virtual key `sk-bf-…`, or infrastructure-issued token where documented

Send Authorization: Bearer <token> unless a route specifies otherwise.

Sign in at https://ageneral.ai to manage projects, members, keys, and agents.
For standalone scripts and servers calling https://models.ageneral.ai, create a virtual key and pass it in Authorization.
Browser sign-in does not replace Bearer tokens for automated Models calls.

OAuth flows for supported clients (for example IDE extensions) are documented on those client pages.

https://models.ageneral.ai accepts:

Credential	Use
Virtual key — prefix `sk-bf-…`	Applications, automation, and integrations you configure
Infrastructure credentials	Traffic from Ageneral-hosted agents; not user-created keys

Example:

Authorization: Bearer <token>

Bearer tokens that use unsupported sk-… shapes return 401 Unauthorized.