xAI (Grok API)

active API / developer platform

xAI's Grok API permits commercial use; API prompts are not used for training by default; Grok Heavy / Premium consumer tiers on X differ in data handling.

xAI provides the Grok model family via API (grok-2, grok-3 etc.). API inputs are not used to train xAI models by default. The consumer Grok experience on X (Twitter) has separate data handling governed by X's privacy policy.

Analysis & practical guidance

The API and Grok-on-X are governed separately

xAI exposes the Grok model family through a developer API. As with OpenAI, the important split is API versus consumer surface: on the developer API, inputs and outputs are not used to train xAI models by default. The Grok experience embedded in X (formerly Twitter) is a different context, governed by X's own privacy policy — do not assume the API's data posture applies to consumer Grok on X.

Practical implications

For application development, the API tier is the one to use — clean no-training default, output ownership with the customer.
xAI is a younger platform than OpenAI or Anthropic; ecosystem tooling, SDK maturity, and region coverage may lag — verify what your stack needs.
If you also use Grok inside X, treat that as a separate data relationship and review X's policy independently.

When to choose it

Choose the xAI API if Grok's capabilities or its tight integration with real-time X data fit your use case. For the broadest ecosystem and tooling maturity, OpenAI and Anthropic remain the safer defaults.

Basics

slug: xai
type: API / developer platform
status: active
last checked: 2026-04-18
official site: https://x.ai
official docs: https://docs.x.ai

Rights

Key	Value	Condition	Source	Checked
`commercial_use_allowed`	yes		xAI Terms of Service	2026-04-18
`output_ownership`	yes		xAI Terms of Service	2026-04-18
`training_use_of_input`	no	API tier only. Consumer Grok on X is governed separately.	xAI Terms of Service	2026-04-18