Quick answer
Choose the xAI API when you are building a repeatable application workflow: submit a request, track a request ID, handle asynchronous status, store the returned asset, and govern credentials and spend. Choose Grok Imagine on the web or mobile apps when an eligible creator wants an interactive generation surface.
They are separate access and billing decisions. xAI’s July 31, 2026 release does not say that a SuperGrok subscription includes API credits or that an API account unlocks every consumer feature.
| Decision | Grok consumer surface | xAI API |
|---|---|---|
| Primary job | Interactive creation | Application and workflow integration |
| Access evidence | grok.com/imagine and mobile rollout; feature eligibility varies by tier, region, and rollout state | API team, key, entitlement, quota, and billing |
| Execution | Product UI manages the job | SDK polls automatically or REST code starts and polls a request |
| Output handling | Creator downloads or uses the product result | Returned URLs are temporary; the application must retain needed outputs promptly |
| Voice reference | Consumer rollout described for eligible U.S. SuperGrok users | Preset voice IDs, up to three, currently restricted to trusted U.S. partners |
| Flowith | Not inferred | Not inferred |
Start with the Grok Imagine Video 1.5 model record if you need the full mode and resolution matrix.
Consumer rollout is not a durable entitlement
xAI said image and voice references started July 31 in the United States for SuperGrok Heavy and SuperGrok Plus on grok.com/imagine and iOS, with broader rollout expected over the following days. The same release described text-to-video and native 1080p as generally available on grok.com/imagine, iOS, and Android.
That dated rollout statement is useful evidence, but it is not a permanent plan contract. Before advising a user to subscribe, check the live account surface for:
- country and device availability;
- current SuperGrok tier names and feature entitlements;
- generation limits, queue behavior, moderation, and output controls;
- price, renewal, refund, and tax treatment;
- current terms for uploaded and generated media.
Do not turn “rolling out” into “available to every account.”
API access is an engineering surface
The current model ID is grok-imagine-video-1.5. xAI documents one active request mode at a time:
- text-to-video from a prompt;
- image-to-video from a prompt and starting image;
- reference-to-video from reference images or permitted preset voices;
- edit-video from an existing video;
- extend-video from an existing video.
The SDK can hide polling, but the underlying job is asynchronous. A REST integration must submit a generation and poll the returned request_id until it is done, failed, or expired. Build timeouts, retries, idempotency, request logging, temporary-URL download, moderation handling, and human review into the application.
Resolution depends on mode
Both access surfaces may expose text-to-video and image-to-video at native 1080p, subject to current entitlement. Do not advertise “all videos are 1080p.” xAI’s developer documentation says:
- text-to-video: 480p, 720p, or 1080p;
- image-to-video: 480p, 720p, or 1080p;
- reference-to-video: capped at 720p;
- editing: source resolution, capped at 720p.
If identity consistency matters more than maximum resolution, test reference-to-video. If a fixed first frame and 1080p matter more, test image-to-video. The reference workflow guide shows how to make that choice.
Voice is the sharpest access boundary
The consumer release shows a character image paired with a voice reference. The public API documentation describes a narrower mechanism: reference_audios selects built-in voice_id values, allows up to three voices per request, and is currently available only in the United States for trusted partners.
Therefore:
- do not promise custom uploaded voice cloning through the documented API;
- do not assume consumer voice eligibility maps to API eligibility;
- obtain authorization for any voice or likeness workflow;
- prevent deceptive impersonation and review xAI’s current terms and acceptable-use policy;
- use a non-voice fallback when the API team lacks access.
Cost and operations checklist
Before selecting a surface, record:
- account, team, region, and plan or API entitlement;
- mode, duration, aspect ratio, and resolution;
- retries, failed jobs, download and storage costs;
- concurrency, latency, quota, and support requirements;
- input-media rights, consent, retention, deletion, and reviewers;
- live price and billing unit from the exact checkout or API pricing surface.
Run the same short prompt set on eligible surfaces. Compare usable outputs per review hour and total delivered-asset cost, not a marketing sample or list price alone.
Frequently asked questions
Is Grok Imagine Video 1.5 available in the xAI API?
Yes. xAI documents grok-imagine-video-1.5 for text, image, reference, edit, and extend video workflows. API jobs are asynchronous, and entitlement, quota, region, pricing, and mode access must be checked for the team that owns the API key.
Do I need SuperGrok to use the API?
xAI’s release presents SuperGrok consumer access and Imagine API access as separate surfaces. Do not assume a consumer subscription supplies API credits or that an API account supplies consumer-plan features; verify each account and billing surface directly.
Which surface supports native 1080p?
xAI says text-to-video and image-to-video support native 1080p in the API and are generally available on grok.com/imagine, iOS, and Android. Reference-to-video remains capped at 720p in the current API documentation.
Is voice reference the same on SuperGrok and the API?
No. The July 31 consumer rollout describes image and voice references for eligible SuperGrok users starting in the United States. Current API documentation limits reference audio to preset voice IDs for trusted partners in the United States; uploaded custom audio is not the documented API input.
When should I choose the xAI API?
Choose the API when you need application integration, repeatable parameters, request IDs, polling, error handling, downstream storage, or governed batch workflows. Choose the consumer surface for hands-on creation when its current plan, region, device, and feature rollout fit your use.
Does xAI access prove Flowith availability?
No. xAI API access, Grok consumer access, and the current Flowith model selector are independent surfaces. This guide does not claim that Grok Imagine Video 1.5 is available in Flowith.
Bottom line
Use the consumer product for interactive creation and the API for controlled integration. Verify live entitlement and price on the exact surface, then respect the mode-specific resolution and voice boundaries.
Official sources
Source check: August 2, 2026. Recheck live rollout, tier, region, pricing, API entitlement, voice access, and documentation before purchase or deployment.