Test your xAI API key.

What this key does

xAI's API is OpenAI-compatible. Grok-2 is the current general-purpose model; Grok-2-vision adds image input. Tool use, streaming, and JSON mode are supported via the standard OpenAI shapes.

How to get a xAI API key

1. Sign in at console.x.ai.
2. Add a payment method.
3. Create a key in the API Keys section.
4. Paste it here to validate.

Common errors and fixes

• 401 Unauthorized: Key is invalid, revoked, or pasted with extra whitespace. Generate a new key from the provider console and try again.
• 403 Forbidden: Key is valid but lacks permission for this resource. Check project / org / workspace scope, or that billing is set up for this key.
• 429 Too Many Requests: You hit the per-minute or per-day rate limit. Wait a moment and retry, or upgrade your tier.
• 404 Not Found: The endpoint or model id changed. Check the provider docs for the current path and model identifier.
• 5xx: The provider is having issues. Check their status page before assuming the bug is yours.

Security best practices

• Store keys in an env var or secret manager — never commit them to a repo, even a private one.
• Restrict scope: prefer per-project or per-deployment keys over a single root key shared across services.
• Rotate on a schedule (90 days is a sane default) and immediately on suspected leak.
• Audit usage in the provider console after rotation to confirm the old key has zero traffic.
• Set per-key spend limits where the provider supports them, so a leaked key has a bounded blast radius.

Pricing at a glance

xAI is mid-tier on price for chat. Image input is billed separately.