Vol. 1 · No. 338Blender 3.6 / 4.2 / 4.5 / 5.0 / 5.2 / 5.3Cycles · EEVEE
JANCTION
Render · Blender on RTX PRO 6000 · Tokyo
0.1 JPYper GPU-secondFirst 100 JPYfree, no card
Front page / Headless Blender on a cloud GPU: render from CI, cron or a script without installing Blender

Headless Blender on a cloud GPU: render from CI, cron or a script without installing Blender

JANCTION Render is Blender running headless on an NVIDIA GPU behind an HTTP API: upload the scene (POST /v1/files), submit a job (POST /v1/jobs) with notify_url for a completion webhook, then download the artifacts. The CLI wraps the same calls (janction-render render scene.blend --wait). The runner needs Python or curl only; Blender (3.6 to 5.3) and the GPU are on our side. AI agents connect at https://render.janction.jp/mcp (remote MCP with OAuth; connecting creates a free key).

Updated 2026-11-17

What it does Your own .blend, bpy script or 3D file (glTF/GLB, FBX, USD, OBJ...) rendered to images or video on a cloud NVIDIA GPU, from an AI app, the terminal or the browser. The first preview needs no payment.
What it does not do It does not speed up the Blender viewport on your machine, does not take non-Blender video, simulations or general GPU jobs, and an AI that is not connected cannot render on its own.

Try your own file for freeBuild it with an AI and try

Browser only; no connector or CLI needed. A 100 JPY welcome credit for a new key (14 days, no card; one per network every 30 days, further keys on the same network share what is left), and 400 JPY more for saving a card that is not charged (once per card); after that, previews stay free up to 2 GPU-minutes a day and finals cost 0.1 JPY per GPU-second.

From a shell or CI step

pip install janction-render
export JANCTION_RENDER_SERVER=https://render.janction.jp
export JANCTION_RENDER_API_KEY=jr_...      # from POST /v1/keys; keep it in the CI secret store
janction-render render scene.blend --frames 1-24 --size 1280x720 --samples 64 --wait --out ./out
ls out/   # output.mp4 (or frames)

The exit code is non-zero when the job fails; the JSON error has error, possible_fix and retryable, so a pipeline can decide whether to retry.

Plain HTTP (any language)

K=$(curl -s -X POST https://render.janction.jp/v1/keys -H 'Content-Type: application/json' -d '{"label":"ci"}' | jq -r .api_key)
SID=$(curl -s -X POST https://render.janction.jp/v1/files -H "X-API-Key: $K" -F file=@scene.blend | jq -r .scene_id)
JOB=$(curl -s -X POST https://render.janction.jp/v1/jobs -H "X-API-Key: $K" -H 'Content-Type: application/json' \
  -d "{\"scene_id\":\"$SID\",\"kind\":\"final\",\"frame_start\":1,\"frame_end\":24,\"width\":1280,\"height\":720,\"samples\":64,\"output\":\"mp4\",\"notify_url\":\"https://ci.example.com/hooks/render\"}" | jq -r .job_id)
# poll GET /v1/jobs/$JOB (status, progress, eta, artifacts[]) or wait for the POST to notify_url
curl -s -H "X-API-Key: $K" https://render.janction.jp/v1/jobs/$JOB/artifacts/output.mp4 -o output.mp4

notify_url receives one JSON POST when the job finishes (https, public host). GET /v1/jobs/{id} is safe to poll every few seconds; eta.human says how long is left and whether the GPU is lent out.

Batch of variants

Upload once, submit many: the same scene_id can be rendered with different frames, sizes, samples, environment presets or orbit settings. Each job counts against the quota separately; POST /v1/estimate with the same body tells you the GPU seconds and whether it fits before you submit.

Limits that matter in automation

  • A welcome credit of up to 500 JPY (100 JPY with no card, 400 JPY more after registering a card, which is not charged) per new key (14 days), then previews free up to 2 GPU-minutes a day and finals at 0.1 JPY per GPU-second from prepaid credit; up to 3,000 frames per instruction (automatically split internally), 1080p on free time and 4K on prepaid credit. A job past the free GPU time left without credit gets 402 payment_required with checkout_url; jobs are not queued for the next day.
  • GPUs available right now: 2 (from /v1/health; 1 more on standby, shared with other work). The number updates itself when GPUs are added. When every GPU is busy, jobs wait and eta.gate says for how long. Build retries with backoff, not tight loops.
  • Results are deleted 24 hours after last use (7 days, normally, for keys that have paid 500 JPY or more in total): download in the same pipeline run.
  • Scripts run with no network; fetch assets through asset_urls, not inside the script.

Connect from an agent instead

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)Plugins (older menu: Customize → Connectors) → Add custom connector → https://render.janction.jp/mcp. "Connect" opens a page that creates a free key
Claude Team / EnterpriseAn owner adds https://render.janction.jp/mcp under Organization settings → Connectors; each member then presses Connect with their own account. In organizations that turn Skills off, Claude Desktop also blocks plugins from November 30 (use the connector URL, or ask the admin to turn Skills on)
ChatGPTPlugins (left sidebar) → Add → Create plugin → https://render.janction.jp/mcp (OAuth). Attach your .blend to the chat. On Business workspaces an admin adds it and shares it
Claude Codeclaude mcp add --transport http janction-render https://render.janction.jp/mcp, then /mcp to authenticate
Claude Code on the web (claude.ai/code)The same connector as Claude.ai: Plugins (older menu: Customize → Connectors) → Add custom connector → https://render.janction.jp/mcp. Works without changing the session's network settings (guide)
Codexcodex mcp add janction-render --url https://render.janction.jp/mcp (the sign-in page opens right away; if Codex later says the server needs login, run codex mcp login janction-render; with a key, add --bearer-token-env-var JANCTION_RENDER_API_KEY)
Cursor / VS CodeAdd to Cursor Add to VS Code Add to LM Studio
The button opens the editor; confirm and it is added. Manual: Streamable HTTP at https://render.janction.jp/mcp
Antigravity CLI / Gemini CLIagy plugin install https://github.com/JasmyLab-JANCTION/janction-render or gemini extensions install https://github.com/JasmyLab-JANCTION/janction-render (the MCP server and the workflow skill)
Kimi Code (Kimi K3 and other models)/plugins install https://github.com/JasmyLab-JANCTION/janction-render (the MCP server and the workflow skill), or add https://render.janction.jp/mcp as a url entry under mcpServers in ~/.kimi-code/mcp.json and run /mcp-config login janction-render (OAuth). Guide
OpenCodeAdd https://render.janction.jp/mcp under mcp in ~/.config/opencode/opencode.json with "type": "remote", then opencode mcp auth janction-render (OAuth). Guide
Qwen Codeqwen extensions install https://github.com/JasmyLab-JANCTION/janction-render (the MCP server and the workflow skill), or qwen mcp add --transport http janction-render with https://render.janction.jp/mcp (stored as httpUrl). Guide
GitHub Copilot CLIcopilot mcp add --transport http janction-render with https://render.janction.jp/mcp, then /mcp auth janction-render in copilot (OAuth). With the skill: copilot plugin marketplace add JasmyLab-JANCTION/janction-render, then copilot plugin install janction-render@janction-render. Guide
DeepSeek Harness (dsh)One @deepseek-ai/dsh-mcp-client entry: transport: streamable-http, url: https://render.janction.jp/mcp, headers Authorization: Bearer with a key from POST /v1/keys (no OAuth). DeepSeek guide (API function calling too)
Grok / Perplexity / Le ChatAdd a custom (remote MCP) connector with https://render.janction.jp/mcp in each app's Connectors settings (Grok: Plugins → New connector → Custom, guide; Perplexity: Settings → Connectors → Custom → Remote, Pro / Max / Enterprise, OAuth; Le Chat: workspace admin, OAuth or a Bearer key)
Gemini app (gemini.google.com)On the web: Settings → Connected Apps → Custom apps, add the MCP URL https://render.janction.jp/mcp (web only, English interface, with activity saving on). Sign-in is the OAuth consent page
ManusConnectors → Create → Add MCP by URL with https://render.janction.jp/mcp (remote MCP only; OAuth or a Bearer key)
MiniMax (MiniMax Code)One streamable-http entry in the MCP settings: url https://render.janction.jp/mcp, and Authorization: Bearer jr_… in headers
Notion (Notion Agent)Business / Enterprise: Settings → Connections → Discover → Add Custom MCP → https://render.janction.jp/mcp, then sign in (the button shows when a workspace admin allows custom MCP servers)
JetBrains (AI Assistant, Junie)AI Assistant: Settings → Tools → AI Assistant → Model Context Protocol (MCP) → Add → connect over HTTP with {"mcpServers": {"janction-render": {"url": "https://render.janction.jp/mcp"}}}. Junie: the same url in ~/.junie/mcp/mcp.json (Authorize opens the browser), or "headers": {"Authorization": "Bearer jr_…"}
Kiro (IDE, CLI) / Amazon Q Developer CLIKiro: "url": "https://render.janction.jp/mcp" under mcpServers in ~/.kiro/settings/mcp.json (in the IDE, open a folder: MCP SERVERS appears in the Kiro panel and the authorization page opens; in the CLI, /mcp auth janction-render). With a key: "headers": {"Authorization": "Bearer ${JANCTION_RENDER_API_KEY}"} (add the variable to Mcp Approved Env Vars). Amazon Q Developer CLI: "type": "http" and the same url in the agent configuration, then /mcp to sign in
Microsoft Copilot StudioTools → Add a tool → New tool → Model Context Protocol → Server URL https://render.janction.jp/mcp. Authentication: OAuth 2.0 with Dynamic discovery, or API key (Header, name X-API-Key, value jr_…). Set the agent's Settings → Generative AI → Orchestration to Yes (generative orchestration), or it will not use the tool
LM Studio (0.3.17 or later)Program tab → Install → Edit mcp.json: {"mcpServers": {"janction-render": {"url": "https://render.janction.jp/mcp", "headers": {"Authorization": "Bearer jr_…"}}}}
Cherry StudioSettings → MCP Servers → Add → Import from JSON: {"mcpServers": {"janction-render": {"type": "streamableHttp", "baseUrl": "https://render.janction.jp/mcp"}}}. Turn it on and press "Sign-in required." to open the consent page in the default browser. If no tools show after signing in, turn the server off and on again (with a key: "headers": {"Authorization": "Bearer jr_…"})
Windsurf, Cline, Goose, Amp, Auggie, Warp, Zed, Roo Code, Continue and other MCP clientsStreamable HTTP at https://render.janction.jp/mcp; OAuth or Authorization: Bearer <api key>
Claude Desktop and other stdio-only clients (npm)npx -y janction-render (in the client's mcpServers: {"command": "npx", "args": ["-y", "janction-render"]}). The npm package janction-render bridges stdio to https://render.janction.jp/mcp with OAuth; --key jr_… for a key you have, --local for the Python stdio server through uv
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

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.

Free limits

Pricing (since 2026-10-08): Each new key gets 100 JPY of GPU time free with no card (1,000 GPU-seconds, 14 days) for previews and finals, and 400 JPY more once a card is saved on a Stripe page that charges nothing (once per card): up to 500 JPY in all. After it is used up or expires, previews are free up to 2 GPU-minutes per key per day and final renders are paid from prepaid credit at 0.1 JPY per GPU-second. Top-ups (paid) start at 100 JPY. The first top-up during the 14-day welcome period counts 1.5x, with the bonus capped at 500 JPY (100 JPY buys 150 JPY of credit). Top-up bonuses are separate from the welcome credit and the card-saving credit. Payment is on a Stripe Checkout page. One full welcome credit per network every 30 days; further keys from the same network use what is left of that network's credit. A job without enough credit gets HTTP 402 payment_required with a checkout_url. Final renders go up to 3,000 frames per instruction (automatically split internally under one job id), 1080p (1920x1080) on free time and up to 4K (3840x2160) on prepaid credit. The free preview time resets at 00:00 UTC (09:00 JST). No sign-up: connecting creates a key. Inputs and results are deleted 24 hours after last use (normally 7 days for keys that have paid 500 JPY or more in total) and never used for training.

FAQ

Does the CI runner need Blender or a GPU?

No. Only Python (for the CLI) or curl. Blender (3.6 to 5.3) and the NVIDIA GPU run on JANCTION's side.

Is there a webhook when the render finishes?

Yes: pass notify_url (https, public host) in the job; the service POSTs one JSON when the job ends. Polling GET /v1/jobs/{id} works too.

Can I keep the API key out of the repository?

Yes. Create a key with POST /v1/keys and store it in the CI secret store as JANCTION_RENDER_API_KEY; revoke it with POST /v1/keys/revoke if it leaks.

Related

Overview · All guides · llms.txt