Skip to main content
GMI Cloud is Zap’s primary live video provider. When a step declares provider: gmi (or defaults.provider: gmi is set) and the run is dispatched with --live, the GMI adapter routes the request to the GMI Cloud request queue API and settles on the flagship BytePlus Seedance 2.0 model (seedance-2-0-260128). This page documents how to obtain a GMI key, wire it into a CLI or web run, and shape recipe steps to match Seedance’s parameters.
GMI keys are bring-your-own-key (BYOK). Zap does not proxy or resell GMI capacity. You must have a funded GMI Cloud account and export the key locally or store it in Supabase before any live run is accepted.

1. Obtain a GMI API Key

1

Sign in to GMI Cloud

Visit console.gmicloud.ai and sign in or create an account.
2

Generate an API key

Open Settings → API Keys and click Create key. Copy the key immediately — it will not be shown again.
3

(Optional) Note your org ID

If your account belongs to a shared workspace, copy the organisation ID from Settings → Organisation. Zap sends it as gmi_org_id when present.

2. Wire the Key Into Zap

Zap accepts the GMI key in two places, depending on where the run originates.

CLI runs — environment variable

Export the key in the shell where zap run --live will be invoked:
Or add to .env.local at your project root (already git-ignored by the zap init scaffold):
Run the doctor command to confirm the CLI can see the key:

Web runs — Supabase vault

For runs initiated from zap.wzrd.tech, the key is stored server-side per creator wallet. See Auth & Secrets for the full flow. Summary:
Keys are encrypted at rest and only decrypted server-side immediately before dispatching the run to GMI.

3. The Seedance 2.0 Model

Seedance 2.0 (seedance-2-0-260128) is the flagship BytePlus video model exposed through GMI. It supports three generation modes: At least one of prompt, first_frame, reference_images, or reference_videos must be present.

Seedance parameters

Pricing (per second of output video)

Zap’s cost planner uses the 720p rate ($0.07/s in the built-in rate table) as the default — override with a step-level model or custom rate if you’re targeting a different resolution.

4. Recipe Examples

All three Seedance modes are expressible as a single video.gen step in a Zap recipe.

T2V — text-to-video

I2V — first-frame animation

Zap’s provider adapter maps the resolved inputs[0] URL to Seedance’s first_frame parameter automatically.

R2V — reference conditioning

5. Raw API Reference

Zap wraps these calls, but you may need to reproduce them directly for debugging.

Submit a request

Response envelope

Poll a request

Zap’s runtime polls this endpoint via Upstash queue workers; you rarely need to call it manually. When you do, use it to confirm asynchronous completion during debugging.

6. Running Live End-to-End

The live run returns a runId; check status with:
Or open https://zap.wzrd.tech/runs/<runId> in the browser for the visual timeline.
Live runs charge your GMI Cloud account immediately when each step is accepted. Always run mock first, confirm the quote, and only pass --live after review. Budget caps in Zap.md are enforced server-side but will not refund a step that has already been dispatched.
  • Providers — how Zap routes each step and the full BYOK secret table.
  • Budget — how the planner quotes and enforces spend before dispatch.
  • Auth & Secrets — storing your GMI key in Supabase for web runs.
  • Step Kinds — all 11 step types and their per-model rates.