Xai API

xAI API (Grok)

When XAI_API_KEY is present in the environment, this app has real xAI API access — use it for AI features instead of mocking responses or reaching for another provider. The same variable is injected into the deployed app at publish, so code built against it works identically in preview and production.

The key is the app owner's personal key: every call spends their quota and credits. Be deliberate about usage — see Spend responsibly before wiring AI calls into anything that runs automatically or is open to visitors.

The key unlocks the full API surface, not just chat:

• Chat / LLM — latest model: grok-4.6; default to it unless the user asks otherwise.
• Imagine (images & video) — generate and edit images, generate video, at runtime inside the app.
• Voice — text-to-speech with expressive voices (and transcription).
• Official docs: docs.x.ai — endpoints, models, parameters, streaming, tool use. Don't guess API shapes; check the docs.
• The API is OpenAI-compatible (https://api.x.ai/v1), so any OpenAI-style client works by switching the base URL and key.

Env vars — do not create a .env file

The key is server-only: read it with process.env.XAI_API_KEY inside createServerFn handlers / server code, never in client components, and never expose it via a VITE_-prefixed variable or an API response.

It can be absent (rollout-gated). Degrade gracefully — check for it and show a friendly "AI features are unavailable" state instead of crashing:

const apiKey = process.env.XAI_API_KEY;
if (!apiKey) throw new Error("AI is not available in this environment");

Calling the API (server-only)

No SDK needed — plain fetch from a server function:

import { createServerFn } from "@tanstack/react-start";

export const askGrok = createServerFn({ method: "POST" })
  .validator((input: { prompt: string }) => input)
  .handler(async ({ data }) => {
    const apiKey = process.env.XAI_API_KEY;
    if (!apiKey) return { ok: false as const, error: "AI is not available" };

    const res = await fetch("https://api.x.ai/v1/chat/completions", {
      method: "POST",
      headers: {
        "Content-Type": "application/json",
        Authorization: `Bearer ${apiKey}`,
      },
      body: JSON.stringify({
        model: "grok-4.6",
        messages: [{ role: "user", content: data.prompt }],
      }),
    });
    if (!res.ok) {
      return { ok: false as const, error: `xAI API error ${res.status}` };
    }
    const body = (await res.json()) as {
      choices: { message: { content: string } }[];
    };
    return { ok: true as const, text: body.choices[0]?.message.content ?? "" };
  });

For streaming, structured outputs, vision, or the full model list, follow docs.x.ai — the shapes are OpenAI-compatible.

Imagine — image & video generation (server-only)

The same key drives runtime image/video features in the app (user avatars, scene art, generated content). Distinct from your build-time image_gen / image_edit tools (the imagine skill): use the API when the running app generates media, the tools when you create static assets while building.

// POST https://api.x.ai/v1/images/generations — same auth header as chat
body: JSON.stringify({
  model: "grok-imagine-image-quality", // or "grok-imagine-image" (cheaper)
  prompt: data.prompt,
  // n (≤10), resolution ("1k"|"2k"), response_format ("url"|"b64_json")
})
// → body.data[0].url

• Image editing: POST /v1/images/edits — natural-language edits, up to 3 reference images.
• Video: grok-imagine-video via the async video endpoints (start, then poll the returned request id; clips up to ~15s).
• Full parameters and examples: docs.x.ai → Imagine API.

Voice — text-to-speech (server-only)

POST https://api.x.ai/v1/tts turns text into spoken audio — narration, accessibility, character voices:

// Same Authorization header; returns audio bytes (e.g. MP3)
body: JSON.stringify({ text: data.text, voice_id: "eve" }) // eve = default voice

List voices at GET /v1/tts/voices (custom voices supported); transcription (speech-to-text) is also available. Details: docs.x.ai → Voice API. Serve the audio to the client from your server function — never call the API from the browser (that would expose the key).

Spend responsibly

The key belongs to the app owner (the user you're building for): every call — including ones triggered by anonymous visitors of the deployed app — spends their personal quota and credits. Burning it on wasteful calls degrades or breaks every other use of their key. Be careful with usage:

• Cap output (max_tokens) and keep prompts small for visitor-facing features. Image, and especially video, generation cost far more per call than chat.
• Never call the API in a loop, on every keystroke, or on page load — make calls user-initiated (button press, form submit) and debounce.
• Cache or persist results (see the neon skill) instead of regenerating the same content per visitor or per render.
• Gate expensive flows — media generation in particular — behind sign-in (authMiddleware, see the auth skill) when the app design allows it.
• Don't add retry storms: on an API error, surface it; retry at most once.