Guides · ai · Popular APIs
Account at console.x.ai, a team, prepaid credits, then an API key with model and endpoint ACLs. Keys can also be created through the Management API.
Researched · not yet run liveLast researched 25 October 2026 · xAI · provider site
An xAI console account belongs to one or more teams; credits, billing and API keys belong to a team.
Several official pages now brand the platform "SpaceXSI API"; the console and docs remain at console.x.ai and docs.x.ai.
Steps marked “human step” are ones only you can do: verapli never signs in, submits, pays or accepts terms for you.
You create the account yourself.
Where: https://console.x.ai/login?mode=sign-up
API use is governed by the Enterprise Terms of Service and the Acceptable Use Policy. You accept them yourself. [to verify where acceptance happens]
Make sure you are in the intended team before billing or creating keys; credits and billing changes apply to the whole team. The team ID is on the team settings page.
Where: https://console.x.ai/team/default/settings/team
Under Billing > API spend management buy credits (card processes immediately, bank transfer 2-3 business days); optionally set auto top-up and a monthly cap. verapli never touches payment details.
On the API Keys page create a key and grant ACLs (e.g. api-key:model:* and api-key:endpoint:*); a key with no permissions fails every request. The full key is not shown again; verapli writes it to your env file.
verapli captures XAI_API_KEY here by plain code: encrypted in your browser, never shown to AI.
Where: https://console.x.ai/team/default/api-keys
In Settings > Management Keys create a management key, separate from inference keys, to create, list and rotate team API keys via management-api.x.ai.
verapli captures XAI_MANAGEMENT_API_KEY here by plain code: encrypted in your browser, never shown to AI.
Plain-English summary, not legal advice. Each card links its source.
The Enterprise Terms require compliance with the AUP and passing equivalent obligations to your own users. The AUP prohibits illegal or abusive uses, reverse engineering, and high-stakes automated decisions about people; violations can lead to suspension or termination. [to verify - pages returned 403 to fetch; based on search summary of official pages] [7]
The Enterprise Terms bar using outputs to train foundation models unless an Order Form allows it, and the Enterprise FAQ says using the API to build a similar or competing service is prohibited. [to verify] [8]
xAI does not refund prepaid credit purchases unless required by law in your region. [3]
| Env var | Secret | Format | What it is |
|---|---|---|---|
XAI_API_KEY | secret | xai-… [to verify] | xAI inference API key for the team |
XAI_MANAGEMENT_API_KEY | secret | [to verify: format not documented]… | Management API key for key, team and billing management |
Source [4]
The same entry as JSON: /api/v1/entries/xai/grok-api · requirements /api/v1/requirements/xai/grok-api · terms /api/v1/terms/xai/grok-api.
claude mcp add --transport http verapli https://verapli.com/mcp
> "What do I need for xAI Grok API, and how long will it take?"
→ tools/call requirements { "provider_id": "xai/grok-api" }Provider rules change. This page is generated from verapli registry version 2026.1025.387; spotted something out of date? Tell us. xAI is not affiliated with verapli.