AI Platforms¶
Connect AI platform accounts to bring token, model, and spend data into CloudVerse AI alongside your cloud AI workloads. For the OpenAI-specific walkthrough, see OpenAI.
Supported platforms¶
| Platform | What you enter |
|---|---|
| Anthropic | API key (an Admin API key is recommended) |
| Mistral AI | Admin API key |
| xAI | Management key and Team ID |
| DeepSeek | API key |
| Z.ai / Zhipu | Region and API key |
| OpenAI | API key |
| OpenAI-compatible endpoint | Endpoint base URL, optional API key, optional expected model ID |
| Kimi, MiniMax, Hugging Face, LangSmith, Groq, Cohere, Together, Fireworks | API key |
Which platforms can actually be validated depends on your deployment. In the connect list, each platform shows tags such as Validation only (the key is checked, but usage export is limited) or Connector unavailable (the platform is listed but cannot be connected yet).
Where to connect¶
- Go to Settings > Integrations and open the AI platforms tab.
- Under Available to connect, select Connect on the platform.
- Enter the fields below, then continue through the discovery step and finish the flow.
You can also ask the in-product Copilot to connect a platform. It shows a connect card in the conversation with the same fields. API keys are typed into the card, not into the chat message.
Note
This tab connects AI platforms as cost sources, so CloudVerse can read your AI spend. It is different from connecting Claude, ChatGPT, or Codex as an assistant that reads your CloudVerse data. For that, see Developer > Connected Assistants.
Field reference¶
Anthropic¶
| Field | Required | Notes |
|---|---|---|
| API Key | Yes | Must start with sk-ant-. Admin keys (sk-ant-admin...) give full cost and usage access. Regular keys (sk-ant-api03...) have limited access. |
Mistral AI¶
| Field | Required | Notes |
|---|---|---|
| Admin API Key | Yes | A Mistral Admin API key. |
xAI¶
| Field | Required | Notes |
|---|---|---|
| Management Key | Yes | An xAI management key. |
| Team ID | Yes | The ID of your xAI team. |
DeepSeek¶
| Field | Required | Notes |
|---|---|---|
| API Key | Yes | A DeepSeek API key. |
Z.ai / Zhipu¶
| Field | Required | Notes |
|---|---|---|
| Region | Yes | International (api.z.ai) or Mainland China (open.bigmodel.cn). Select the region your account uses. |
| API Key | Yes | A Z.ai API key. |
Z.ai / Zhipu has no programmatic historical billing export.
OpenAI-compatible endpoint¶
For self-hosted or third-party models that expose an OpenAI-compatible API.
| Field | Required | Notes |
|---|---|---|
| Endpoint base URL | Yes | Must start with https://, for example https://models.example.com. |
| API key | No | Only if your endpoint requires one. |
| Expected model ID | No | The model name you expect the endpoint to serve. |
Single-key platforms¶
OpenAI, Kimi, MiniMax, Hugging Face, LangSmith, Groq, Cohere, Together, and Fireworks each take one field.
| Field | Required | Notes |
|---|---|---|
| API Key | Yes | An API key for the platform. |
After you connect¶
AI platform connections finish with a discovery step. CloudVerse registers a single account for the platform, so there is nothing to choose; confirm it and complete the flow.
Then open Cost Management > AI Economics and filter by the platform to confirm data appears. See AI Economics.
Best practices¶
- Prefer the most restricted key that still exposes usage and cost data.
- Rotate keys on schedule and update them in CloudVerse promptly.
- Do not paste API keys into tickets, chat messages, screenshots, or documentation.
See Integration setup issues if data does not appear after setup.