Skip to main content
Ageneral splits traffic across two HTTPS hosts. Each host accepts different credentials.

​
Hosts and credentials

HostPurposeTypical credential
https://ageneral.aiConsole-backed APIs: projects, members, keys, agentsBearer token from sign-in
https://models.ageneral.aiOpenAI-compatible Models inferenceVirtual key sk-bf-…, or infrastructure-issued token where documented
Send Authorization: Bearer <token> unless a route specifies otherwise.

​
Console and scripts

  1. Sign in at https://ageneral.ai to manage projects, members, keys, and agents.
  2. For standalone scripts and servers calling https://models.ageneral.ai, create a virtual key and pass it in Authorization.
  3. 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.

​
Models host details

https://models.ageneral.ai accepts:
CredentialUse
Virtual key — prefix sk-bf-…Applications, automation, and integrations you configure
Infrastructure credentialsTraffic from Ageneral-hosted agents; not user-created keys
Example: 
Authorization: Bearer <token>
Bearer tokens that use unsupported sk-… shapes return 401 Unauthorized.

​
Next steps

  • Models — endpoints and identifiers
  • Quickstart — first Models request
  • Agents — how agents access Models
  • Usage and billing — credits and wallet behavior
  • API reference tab — Models, Projects, Agents