Agent-generated 3D: from a text prompt to a rendered image or MP4

Updated 2026-10-05

An agent does not need Blender to make 3D: it writes a bpy script that builds the scene, sends it to JANCTION Render, and gets a 720p preview back in a few GPU seconds. It looks at the image, fixes the script (camera, scale, lights, materials), repeats until it looks right, asks the user, then renders the final frames or an MP4. The preview is cheap on purpose, so the loop costs almost nothing.

The loop

  1. scene_info reads the scene without rendering: cameras, frame range, objects, missing files.
  2. render_preview renders 1-4 frames at 720p in a few GPU seconds and returns the image, so the agent can look, fix the script and try again.
  3. render_estimate says how long the final render takes ("about 3 minutes") and whether it fits today's free quota.
  4. render_final renders the frames on GPUs and joins them into an MP4; render_status reports the remaining time; render_download returns the files or links.

In practice an agent needs two or three previews before a scene looks right. Each is a few GPU seconds, so a whole session fits easily in the free quota.

What agents get wrong, and what to tell them

Prompt patterns that work

Using JANCTION Render, build a glossy red cube rotating on a grey floor and show me a 4-frame preview.
If it looks right, render 24 frames at 1280x720 as an MP4.

To render a .blend or 3D file that is on your computer, drop it at /upload to get a 12-hour link (no sign-up) and tell the AI "Render this file: <link>". To test the connection first: "Render a preview of https://render.janction.jp/samples/cube_scene.py".

"Make a product shot of a ceramic mug on a wooden table, studio lighting, preview it, then give me a 48-frame turntable MP4." · "Build a low-poly city block with 20 buildings and a camera fly-through; preview frames 1, 12, 24; then render 24 frames at 720p."

A 4-frame preview rendered by JANCTION Render (a rotating red cube)
The 4-frame preview Claude.ai got from that prompt: 4 GPU seconds. The 24-frame 720p MP4 that followed took 58 GPU seconds (2026-10-01, RTX PRO 6000).

How long it takes

jobGPU timenote
preview, 4 frames (720p split in 4 tiles, 16 samples, denoised)about 4 sround trip about 8 s; the image comes back inline
final, 24 frames at 1280x720, 64 samples → MP4about 60 smeasured 2026-09-30 / 10-01 (59 s and 58 s)
final, one 1920x1080 frame at 128 samplesabout 11 sthe estimator's baseline; heavy scenes take longer

These are individual observations of simple scenes (2026-09-30 to 10-01 UTC, NVIDIA RTX PRO 6000 Blackwell Max-Q Workstation Edition, 96 GB). The 4-GPU-second example used a rotating cube, four 640x360 tiles and 16 samples. GPU time includes Blender startup and scene loading; it is distinct from completion time including queue and transfers. See conditions, round trips and reproduction files. These are not speed guarantees.

render_estimate gives the number before rendering; once a scene has been rendered once, the estimate uses that scene's own measurement.

Connect

fromhow
A file on this computer (.blend, 3D file)Drop it at /upload to get a 12-hour link (no sign-up), then tell the AI "Render this file: <link>". From inside Blender use the add-on; from a terminal the CLI uploads directly
Claude.ai (web / desktop / mobile)Settings → Connectors → Add custom connector → https://render.janction.jp/mcp. "Connect" opens a page that creates a free key
ChatGPTSettings → Connectors → Advanced → Developer mode → Create → https://render.janction.jp/mcp (OAuth)
Claude Codeclaude mcp add --transport http janction-render https://render.janction.jp/mcp, then /mcp to authenticate
Codexcodex mcp add janction-render --url https://render.janction.jp/mcp
Cursor / VS CodeAdd to Cursor Add to VS Code
The button opens the editor; confirm and it is added. Manual: Streamable HTTP at https://render.janction.jp/mcp
Gemini CLI / Antigravity CLIgemini extensions install https://github.com/JasmyLab-JANCTION/janction-render
Grok / Perplexity / Le ChatAdd a custom (remote MCP) connector with https://render.janction.jp/mcp in each app's Connectors settings (Grok: New Connector → Custom; Perplexity: Pro / Max / Enterprise; Le Chat: workspace admin)
Windsurf, Cline, Goose, other MCP clientsStreamable HTTP at https://render.janction.jp/mcp; OAuth or Authorization: Bearer <api key>
Terminal (stdio, sends local files)claude mcp add janction-render -e JANCTION_RENDER_SERVER=https://render.janction.jp -- uvx --from janction-render janction-render-mcp
Inside Blender (for people)The add-on; extension repository https://render.janction.jp/extensions/index.json. Maya / Houdini / Cinema 4D: submit tools

Free limits

Free beta (as of 2026-10-01): 10 GPU-minutes per key per day (20 per network), final renders up to 240 frames at 1080p. Quotas reset at 00:00 UTC (09:00 JST). New jobs exceeding the quota are rejected with HTTP 429 quota_exceeded and resets_at; they are not queued for the next day. Resubmit after the quota resets. No sign-up: connecting creates a key. Inputs and results are deleted 24 hours after last use and never used for training. Paid plans will be announced on this site and in llms.txt before they start.

FAQ

Can an AI generate a 3D scene from text with this?

The agent generates the scene as a bpy script (Blender's Python), and JANCTION Render renders it. There is no text-to-3D model inside; the quality comes from the agent's script and the preview loop.

How many previews does a typical scene take?

Two or three. Each is a few GPU seconds (4 s for a simple scene), so even ten previews stay far inside the daily free quota.

Can the agent see the preview?

Yes. In MCP the preview comes back as an image the agent can look at (and as an interactive panel in clients with MCP Apps); over HTTP it is a PNG link.

Related

Overview · llms.txt

JANCTION Render v0.4.17 · JasmyLab Inc. · Updated 2026-10-05 · Tested with Blender 5.0, JANCTION Render 0.4.17 · 日本語