3D Render Pro

The 3D Render Pro node authors an animated 3D scene from a brief and renders it, in one run, on a hosted build engine. One run returns the finished MP4, the exact scene it was rendered from, and one still image per shot. It is a different node from Generate 3D Scene: that node is a cheap, editable clay previz whose MP4 comes from a separate Render Video run.

3D Render Pro runs only on Nodaro Cloud, and only while the Cloud's 3D engine offers it. Self-hosted editions do not offer this node.

When to use it

• You want a finished 3D shot from a brief in one step, not a previz to render later.
• You want to export an existing scene again, without paying to author it again.
• You want one still per shot, to use as image references for later generations.
• You want a wide 21:9 frame, which Generate 3D Scene does not offer.

Where it is available

• Node picker. On Nodaro Cloud, the node is under Video › Titles, Graphics & Captions › 3D Render Pro while the 3D engine offers it. When the engine is not available, the node is not listed at all, rather than shown and disabled.
• API and SDK. GET /v1/3d-scene/capabilities reports pro.available. Where the node is unavailable, GET /v1/nodes leaves it out, and a request is refused with 503 SCENE_CAPABILITY_UNAVAILABLE. It never falls back to the Basic engine.
• MCP. The pro_3d_render tool is listed only where the node can run, so its presence in the tool list is the check.

A workflow that already contains the node keeps its stored scene and video if the engine is later switched off. Only new runs are refused.

Quick start

The scene source

Every run has exactly one source, and the source decides both what happens and what you pay.

An empty Edit instruction (optional) is what makes a run render-only. Through the API, leave the editPrompt field out for a plain export: an empty string is a different request.

A fourth source, a completed export from a paired desktop Blender, is available through the API where the install supports it.

Inputs

Outputs

Connect video nodes to Video, not to Composition: the composition is a scene, not a video.

The stills are a contact sheet, not a second render. They come out of the same run at no extra cost. A single-shot scene has exactly one still, at frame 0. Use them to feed a shot's opening frame to an image or video model, or to review the blocking shot by shot without scrubbing the MP4.

Stills work in any image input. The stills are stored privately. When you connect the Stills output to an image or reference input, Nodaro gives the model a short-lived read of the exact still it needs. The read is for that run only and is based on your own access. The link expires minutes later and is never stored.

Settings

There is no model or reasoning setting: the planner is fixed and run by Nodaro. The style is clay.

Timing of an existing scene. A scene already has its own duration, frame rate and aspect ratio, and a run keeps them. Tick Re-time this scene to change them on purpose. A change that does not fit the scene is refused rather than applied silently.

Use the result as a video reference

The MP4 is a layout reference, like the render of Generate 3D Scene. It carries the positions, the occlusion, the framing, the camera move and the timing, and also a grey clay look that a video model copies unless told not to.

• Nodaro adds the scoping line. Wire the Video output into the Video Refs input of a Generate Video node. Nodaro then adds a line that tells the model to copy only the layout and to ignore the clay look. For a scene with several shots, the line also names the cut points.
• One character per figure. Photoreal treatment follows each referenced subject. Give every figure that must look real its own character reference, and keep two reference slots free for a location or a style image.
• You are told about uncovered figures. When a workflow run finds more people in the scene than character references, it still runs, because you may want clay figures. It records a scene3d_unreferenced_figures warning on the job, with the number of uncovered figures and whether one reference per figure fits the model's reference limit.
• Never the start frame. Wire the render into a reference input. A start frame sets the look, and no scoping line reaches it.

Credits

3D Render Pro is one billable operation. A new scene pays for the authoring, the hosted build and the render. An existing scene without an edit instruction pays for the render only. Each repair pass inside the correction budget is paid work.

Quote, then run. The price is set by each deployment, so there is no fixed list price. Every run is quoted first, and the quote shows a ceiling, not a charge. On the canvas, the node shows it as Up to N credits. Allowances that a run does not use are released when it settles. An install with no configured price refuses the run before reserving anything.

The quote can include two allowances besides the repair passes:

Frame size and length. The render stage is priced per output frame, so a longer scene or a higher frame rate costs more. The price per frame follows the same frame-size ladder as Render Video. Frames up to 1920 pixels on the longest side use the base rate. Larger frames cost 1.5 times the base up to 5.12 megapixels, and 2.5 times above that.

Rendering a stored scene again, through Render Video or with Existing scene and no instruction, is billed as an ordinary render. Work completed before a failure, such as an earlier repair pass, is charged as usual.

What happens when a run does not pass

A visual review checks the built scene, and repair passes answer its objections for as long as the correction budget lasts. A run ends in one of these ways:

When a scene is delivered without approval, the run completes, the MP4 is real and the credits are charged. Use it as it is, or treat the review's correction as an edit brief: run Existing scene with that correction as the Edit instruction, which pays for another authoring pass. Direct edits, such as moving, recoloring or hiding objects, are free. A scene that nobody reviewed has no correction to work from, and running the same job again authors a new scene, so judge the MP4 yourself.

When a run fails but keeps its draft, there is no MP4, but the draft is an ordinary scene revision:

• Render it as it is. Run it as an Existing scene with no instruction. That run pays only for the render, and its own checks do not re-judge the draft.
• Fix it yourself. Direct edits apply to the draft like any other scene and cost no authoring.
• Author again from it. Run it as an Existing scene with an edit instruction.

Keeping the draft costs nothing. On the canvas, the node shows the draft and the failure together, also after a page reload, so a scene being present never means the run passed. An edit you made while the run was in progress still wins, and the arriving draft is kept in the revision history.

Planning errors

Tips

• Previz first, then Pro. Block the shot cheaply with Generate 3D Scene and Edit 3D Scene, then render the final version here.
• Export again without authoring. To export the same scene again, use Existing scene with no instruction, or connect Composition to Render Video.
• Lower the budget for drafts. A Correction budget of 0 or 1 limits the paid repair work.
• Use the stills. Each shot's still is a ready-made image reference for Generate Image or Generate Video.

From the API

The API uses two calls for one paid job. POST /v1/pro-3d-render/quote takes the request and returns a quoteId and maxCredits, the ceiling. Quoting reserves and spends nothing. POST /v1/pro-3d-render then takes the same body plus the quoteId, with an Idempotency-Key header of 8 to 255 characters, and returns a jobId. A body changed between the two calls is refused, and so is an expired quote. Reuse the same Idempotency-Key when you retry a submission that timed out.

const caps = await client.scene3d.capabilities();
if (!caps.pro?.available) return; // this install cannot run it

// Author a new scene and render it: quotes and runs in one call.
const shot = await client.scene3d.renderProAndWait({
  source: {
    kind: "prompt",
    prompt: "A red suitcase rolls behind a central pillar and reappears. Dolly right over thirty seconds.",
    references: [{ id: "look", kind: "image", role: "appearance", url: appearanceImageUrl }],
  },
  durationSeconds: 30,
  fps: 24,
  aspectRatio: "21:9",
  maxRepairPasses: 2,
});

// Later: render the same revision again, with no authoring charge.
await client.scene3d.renderProAndWait({
  source: { kind: "scene", revisionId: shot.sceneRevisionId, sourceJobId: shotJobId },
});

• The completed job carries videoUrl, scenePlan, sceneRevisionId, shotStills (one { shotIndex, frame, assetId, url } per shot), validation and metadata with the frame size, frame rate, frames and duration.
• An unapproved delivery adds metadata.review. Check that field and its verdict, refused or unavailable, rather than validation.status, which is passed in both cases.
• A failed job with a draft still has scenePlan, sceneRevisionId and a validation whose status is failed.
• Frame rate. Through the API, fps can be any value from 15 to 60.

AI assistants use the pro_3d_render MCP tool, which quotes and submits with the same parameters. See 3D scenes through MCP and the 3D scenes API for every field, warning code and error.