ToAPIs
home

Quick Answer

  • grok-video-1.0 supports Text-to-Video, Image-to-Video, R2V, and Video Edit in one workflow.
  • Use this model guide page to validate parameters with minimal request/response examples.
  • Stabilize prompts here first, then move to production API integration.

Key Parameters

  • model | string | required | grok-video-1.0 | - | Model identifier. Use the fixed value `grok-video-1.0`.
  • prompt | string | required | - | - | Main instruction describing the subject, action, scene, and style.
  • aspect_ratio | string | optional | 16:9 | 1:1 | 16:9 | 9:16 | 3:2 | 2:3 | Video aspect ratio. Defaults to `16:9`; supports `1:1 | 16:9 | 9:16 | 3:2 | 2:3`.
  • duration | integer | optional | 6 | 6 | 10 | Output duration in seconds. Defaults to `6`; supports `6 | 10`.
  • resolution | string | optional | 720p | 480p | 720p | Output resolution. Defaults to `720p`; supports `480p | 720p`.

Common Errors

  • 400 invalid_request_error: trigger=Request payload misses required fields or has invalid field types.; fix=Validate model, mode, and input schema before request.; retry=Retry only after fixing payload; avoid blind retries.
  • 401 authentication_error: trigger=Missing Authorization header or invalid API key.; fix=Verify Bearer token format and API key scope.; retry=Retry after auth fix; rotate key if repeated failures continue.
  • 429 rate_limit_exceeded: trigger=Request rate, concurrency, or current quota hits upstream rate limiting.; fix=Apply exponential backoff first, then review request rate, concurrency, and quota usage.; retry=Use exponential backoff (e.g., 1s/2s/4s) with jitter; if it persists, reduce submission pressure.
  • 500 internal_error: trigger=Transient upstream error or internal processing failure.; fix=Capture request id and trigger retry workflow.; retry=Retry 2-3 times with short delays; escalate if persistent.

grok-video-1.0

grok-video-1.0 is provided by xAI with Video capabilities. Current pricing reference: 2 クレジット /second. This page helps you understand positioning, parameters, and production-ready use cases before integration.

モデルタイプ：
料金： 2 クレジット /second

入力

フォームJSON

参照画像

主体、カメラ、シーン、スタイルを説明してください。150 / 1200

詳細オプション

サンプルパラメータ

出力

プレビューJSON

生成した動画がここに表示されます

動画生成には時間がかかる場合があります。送信後、ポーリングが完了するまでお待ちください。

API ドキュメントを見るAPI キーを取得

生成には時間がかかります。しばらくお待ちください。このページを離れても、[ タスクログ ] で生成した内容を直接確認できます。

リクエストをプレビュー

{
  "model": "grok-video-1.0",
  "prompt": "A 6-second product concept video generated with grok-video-1.0: a futuristic city street, slow camera push-in, natural light, stable cinematic motion.",
  "duration": 6,
  "aspect_ratio": "16:9",
  "resolution": "720p"
}

透明な料金体系

grok-video-1.0 の料金

Video usage is billed according to the current duration and resolution rules. Final billing follows the current account quote.

クレジットを追加
2 クレジット /second

ToAPIs を選ぶ理由

Why call grok-video-1.0 through ToAPIs?

Keep video generation, API keys, billing, and task tracking in one workflow.

Unified multi-mode testing

Switch across Text-to-Video, Image-to-Video, R2V, and Video Edit in one place.

Parameter-first validation

Iterate quickly on prompts, durations, and references before production rollout.

Production-ready handoff

Minimal request/response structure helps you move stable configs into API workflows.

Connect in three steps

Create a key, submit a video task, and poll the result.

  1. 1

    Step 1

    Fill prompt and key parameters.

  2. 2

    Step 2

    Run, inspect output structure, then iterate.

  3. 3

    Step 3

    Move stable settings into production API.

When to use grok-video-1.0

Use case 1

When you need fast iteration across multiple generation modes.

Use case 2

When you need to validate parameters and error handling before integration.

よくある質問

grok-video-1.0 FAQ

When should I use grok-video-1.0?

Use it to validate video concepts quickly, compare mode behavior, and converge prompts before API rollout.

How do I choose Text-to-Video vs Image-to-Video?

Use Text-to-Video when you only have instructions; use Image-to-Video when you already have key frames or composition.

What is the difference between R2V and Video Edit?

R2V focuses on reference-guided generation, while Video Edit focuses on modifying existing video assets.

Image or video model error: invalid apitype: -1

This usually means the request was sent to the wrong endpoint. Image and video models typically do not use the chat endpoint. Instead, submit the documented HTTP task request and poll the task status endpoint for results. Check the actual request code, URL, and payload first.

An image or video task failed, but the user was still charged

Ask the user for the task log or screenshot first and check whether input or output token usage appears. If token accounting shows up, the request was likely sent through a chat endpoint instead of the proper media workflow. Image and video models usually run as async HTTP task APIs: submit the task first, then poll by task id according to the relevant docs.

grok-video-1.0 API

Start building with grok-video-1.0

Test a video request here, then continue in the dashboard or API documentation.

Start for freeView API Docs

Try grok-video-1.0 with one ToAPIs key.

Use one account and API surface for video generation workflows.

Sign up to get free credits