Vivix W1: Asynchronous Video API vs Private-Beta Interactive Worlds

One brand, three different product contracts

Vivix W1 is a model family from Vivix. It is not Vidu; their model identifiers, billing and demonstrations must not be interchanged. This profile helps a developer decide whether the documented job API or a separately approved live-world workflow fits the output they need.

Swipe wide tables horizontally on a phone.

Check the models returned for your own authorized key with GET /v1/models; the result is workspace-scoped. W1 Streaming World appears only where access is approved. An example accepting the string in documentation does not prove your account can run it. We did not create an account or check a private workspace. API introduction · Models and access.

Asynchronous W1 inputs and downloadable output

Swipe wide tables horizontally on a phone.

These limits come from the W1 video API guide. The listed reference fields cover images and audio; a broader research demo is not evidence that this API accepts reference-video uploads. Respect the rights and privacy of people in source material.

Create once, save the job ID, then poll

The following JSON is a request-body example for POST https://api.vivix.ai/v1/videos/jobs. Authentication uses your own authorized Bearer key. This example was checked as JSON only; we did not submit it or generate a clip.

{
  "model": "vivix-w1",
  "jobs": [
    {
      "prompt": "An empty coastal landscape at sunrise, camera slowly moving forward.",
      "duration": 8,
      "aspect_ratio": "16:9"
    }
  ]
}

1. Choose a model your workspace can use and check the W-credit balance and limits. Standard W1 is the baseline option; the other IDs buy documented speed tiers.
2. Create the job and save the returned job identifier. Vivix's REST envelope uses code, message and data; code: 0 denotes success. Inspect both transport status and the response body.
3. Query GET /v1/videos/jobs/{job_id}. Wait a few seconds between polls while status is queued or processing.
4. On succeeded, use video_url for the final MP4. On failed, inspect the error and stop the loop. A job ID or a successful POST is not a delivered video.

For a timeout after creation, first establish whether a job exists; do not blindly repeat a potentially billable POST. Preserve X-Request-ID and X-Trace-ID for support. The guide lists bad parameters (20004), MIME mismatch (20008), moderation rejection (30001 / HTTP403), not-found responses and HTTP429 rate/concurrency limits. Correct inputs or access rather than retrying permanent errors. Failed generation can report generation_failed, generation_timeout or generation_cancelled. Refund and retry charging conditions remain an account check. Job states and errors.

A live world is a different integration

The Streaming World configuration describes POST /v1/streaming-world/sessions with model: vivix-w1-stream, then real-time events that control a continuing session. A Session is the runtime resource; this is not a CRUD service for stored world objects. Use the capabilities returned for the approved session as the contract for supported controls and inputs.

Example distinction: a social producer who wants an eight-second vertical MP4 can evaluate an asynchronous video job. A game prototype that needs the scene to change while a user interacts needs live-world access, a session client and a separate latency/control evaluation. Polling an async job faster does not turn it into an interactive world.

The current release is private beta and limited to approved workspaces. Public schema documentation does not establish public availability, production support, a universal quota or an async-equivalent price. A1 Streaming Avatar is not a workaround that silently supplies the same W1 scene-generation contract. Streaming World configuration.

Keep dollars, W credits and promotions separate

Swipe wide tables horizontally on a phone.

Official platform price display · API credits and promotional terms. W credits and A credits are separate balances and cannot be treated as interchangeable. A dollar promotion, an account's included allowance and its W-credit conversion are different facts; we have not verified a public conversion tying them together.

For an eight-second output, the documented units are 8 W credits at standard, 24 at Fast or 32 at Ultrafast. This is arithmetic in credits, not a dollar quote or a prediction of your invoice. Ask what is billed for failures, retries, reference material after the waiver and any workspace minimum before spending.

When to shortlist W1—and when to choose another workflow

Shortlist the async route when you need a generated 5–15-second clip, can supply permitted prompt/reference material and can tolerate a queued job. Evaluate standard before paying for faster tiers. Vivix says the tiers share video quality and differ in speed/cost; that is a vendor statement, not our verified equivalence result.

Look elsewhere or wait for access when you need a guaranteed publicly available live interactive world, deterministic long-form scene continuity, an existing-footage editor, or a talking-avatar pipeline. Use HeyGen for an avatar-oriented comparison and our video generator guide for other short-clip choices; compare their own access and licence terms separately.

The platform advertises performance and price advantages, including “80x” language. Its comparison uses specific benchmark conditions and mixed competitor billing references. Those are vendor claims, not our independent benchmark or proof that your queued jobs will have the same latency. Official demonstrations illustrate possibilities, not repeatable reliability across your prompts. We downloaded no weights or demo files, bought no credits and ran no video calls.

Next step: confirm your workspace's model access and effective billing, then design a small rights-cleared trial with acceptance criteria for scene consistency, prompt following, audio and export. A real trial requires separate account, material and spending authorization.