AI Connectors
Cloud Ctrl can connect directly to AI providers to import AI usage and spend, so AI consumption sits alongside your cloud spend in the same views, reports and allocation models.
The supported providers are:
| Provider | Credential required | Data imported |
|---|---|---|
| OpenAI | Admin API key (sk-admin-…, api.usage.read scope) | Organization bill + usage log |
| Anthropic | Admin API key (sk-ant-admin-…) | Organization cost report + usage report |
| GitHub Copilot | Access token (manage_billing:copilot, read:org) | Billing report + premium-request usage |
| Cursor | Admin API key (crsr_…, Enterprise teams) | Full per-request usage log |
| xAI | Management key (Billing read access) | Team billing usage, daily by model |
| OpenRouter | Management key (not an inference key) | Account activity by model + provider |
Attribution at a glance
AI providers differ in what they can attribute. If a dimension matters to you, check it is supported before choosing a connection:
| Spend by user | Spend by API key | Spend by model | Project / workspace | Token counts | |
|---|---|---|---|---|---|
| OpenAI | ✓ | ✓ | ✓ | ✓ Project | ✓ |
| Anthropic | ✗ | ✓ | ✓ | ✓ Workspace | ✓ |
| GitHub Copilot | ✓ | ✗ | ✓ | ✓ Cost centre / repo | ✓ |
| Cursor | ✓ (exact) | ✓ | ✓ | ✗ | ✓ |
| xAI | ✗ | ✗ | ✓ | ✗ (team only) | ✗ |
| OpenRouter | ✗ | ✗ | ✓ (+ upstream provider) | ✗ (account only) | ✓ |
Where a provider can't attribute spend to a user or key directly (OpenAI, Anthropic), Cloud Ctrl shares each day's charge across the users/keys that were active — the shares always add back up to exactly what the provider billed. For providers with no breakdown at all (xAI, OpenRouter), spend lands at the team/account level; see each provider's page for workarounds.
Experimental opt-in
Warning
The AI connectors are currently experimental. They are hidden on the Cloud Connections page until the tenant opts in to the experimental program.
To enable them:
- Open Settings → General
- Tick the Experimental checkbox (the "AI Connections" experimental feature)
The AI providers then appear under Settings → Cloud Connections.
How it works
Connecting an AI provider is the same two-step flow used for the cloud vendors:
- Add a Credential — the admin/API key for the provider (see the provider's page for exactly where to create it). Keys are stored encrypted and are never displayed again after saving — only the last four characters are shown as a hint.
- Add a Cloud Account — links the credential to a specific organization/team/account to import.
Most providers let you choose how many days of history to pull on first activation (default 90 days). After the initial backfill, usage is imported per calendar month.
Tips
Usage and costs are imported in the provider's billing currency (typically USD). Cloud Ctrl converts everything to your tenant's display currency.
Where to see the data
Once at least one AI connection exists, an AI Usage entry appears under Cloud Intelligence in the navigation with four tabs:
- Overview — total AI spend and trends
- Models — spend and usage broken down by AI model
- Users — spend and usage attributed to individual users
- API Keys — spend and usage attributed to API keys
Each row of imported AI usage is tagged with the reserved system dimensions AI User ($aiuser), AI API Key ($aikey) and AI Model ($aimodel) — plus AI Project, AI Repository and AI Cost Centre where the provider supports them. These are available for tag mapping and reporting like any other dimension. Usage that cannot be attributed rolls up under $Unassigned.
Getting started
Choose your AI provider: