Skip to main content
PixVerse R2 Director makes a film one clip at a time. First create the world from a description, up to six reference images, or both. Give it one of three styles: Dramatic, Ambient, or POV. Then send a prompt for each clip. Each prompt becomes a 5 to 10 second clip that continues from the last frame of the one before. A clip can also cut to one of your reference images, or move from one image to another. The model builds clips and plays them in separate steps. A built clip waits as ready until you play it or autoplay plays it. Between clips, the picture holds on the last frame. The model also keeps every clip as a step result of the session, with its video, its last frame, and its prompt. You can generate clips from the same world more than once. Save its world_id and attach the world in a later session, so you do not have to create it again. The PixVerse R2 Director reference has four pages: this overview; the schema, which lists every command and message; the prompt guide, which covers world descriptions and clip prompts; and the tutorial, which shows how to create a world, queue clips, and play them. PixVerse R2 Director uses the same wire protocol as every other Reactor model. You open a session with the Reactor class, send named commands, and receive messages. Its model name is reactor/pixverse-r2-director. The @reactor-models/pixverse-r2-director typed SDK adds named methods and React hooks on top of the same protocol.

At a glance

Pass the model name, reactor/pixverse-r2-director, to the SDK. A session token uses the same name as its scope. The short slug, pixverse-r2-director, names the docs folder, the typed SDK, and the row for this model on Pricing and billing.

Key features

Worlds from text and images

Describe the world, add up to six reference images, and pick a style: Dramatic, Ambient, or POV.

Clips that continue

Each clip continues from the last frame of the one before. A clip can also cut to a reference image, or move from one image to another.

A queue and a player

Queue prompts while clips build. Play ready clips one at a time, or turn on autoplay. The model keeps every clip as a step result.

Quick start

Create a session token on your server. Then connect with the base JavaScript SDK or the @reactor-models/pixverse-r2-director typed SDK. Do not put your rk_ API key in browser code. To create tokens, see Authentication.

How it works

  1. Connect to reactor/pixverse-r2-director. The first session_state has phase idle.
  2. Call create_world with a description, reference images, or both. Or call attach_world with a saved world_id. The phase changes to world_ready.
  3. Call enqueue with a prompt for each clip. The first enqueue on a world starts a run. The model builds the clips in order. When a clip is ready, the model sends clip_generated.
  4. To send a ready clip on main_video, call play. Or turn on set_autoplay, and ready clips play on their own, oldest first.
  5. End the run with end_run, or let it end on its own. Built clips stay ready after the run ends. The next enqueue starts a new run on the same world.
For playback without gaps, let about 30 seconds of clips become ready before you play them or turn on autoplay. Between clips, main_video holds the last frame.