Blender renders headless with blender -b scene.blend -f 1 (or -P script.py), so an API around it is a queue that runs that command on a machine with an NVIDIA GPU, stores the frames, and hands out links; the work is everything around it: installing Blender and drivers, keeping GPU memory from one job leaking into the next, sandboxing user scripts, estimating time, retrying, and paying for a GPU that sits idle between jobs. JANCTION Render is that API already running on datacenter GPUs: POST a .blend, a bpy script or a 3D file, get a tiled preview in seconds, an estimate, the final frames or MP4, a webhook, and an MCP server for AI agents, with 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, then 0.1 JPY per GPU-second (previews free up to 2 GPU-minutes a day); finals go up to 3,000 frames per instruction (automatically split internally), 1080p on free time and 4K on prepaid credit. Build your own when the farm must stay inside your network or runs all day; call the hosted one when jobs are bursty, an agent drives them, or there is no GPU at hand. AI agents connect at https://render.janction.jp/mcp (remote MCP with OAuth; connecting creates a free key).
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.
| Part | Doing it yourself | On JANCTION Render |
| Machine | an NVIDIA GPU box (cloud VM or on-prem), drivers, Blender 5.x, ffmpeg for video | NVIDIA RTX PRO 6000 (96 GB) in a datacenter, Blender 5.0, 5.2 and 5.3, plus 3.6, 4.2 and 4.5 (a .blend opens with the version it was saved in), ffmpeg |
| Running a job | blender -b scene.blend -o //out/ -F PNG -f 1 or blender -b -P script.py; a worker loop; one job at a time per GPU | POST /v1/jobs or render_final; frames are split into chunks and queued |
| Isolation | a bpy script can read any file and open the network; you need your own isolated sandbox per job | each render runs in an isolated, throw-away environment, and scripts are checked before they run; security |
| Previews and estimates | write them: a low-sample tiled render, and a time model from past jobs | render_preview (1 to 4 frames in one image, a few seconds), render_estimate from measured per-frame times |
| Delivery | object storage, signed URLs, expiry, MP4 assembly | signed links valid 24 hours, MP4 / WebM / ProRes / GIF / WebP assembled, share pages |
| Agents | wrap the API as MCP tools yourself | remote MCP (OAuth) at https://render.janction.jp/mcp, stdio package on PyPI, tool descriptions written for agents |
| Cost | the GPU is paid for whether it renders or idles | welcome credit of up to 500 JPY per new key, then 0.1 JPY per GPU-second, metered (previews free up to 2 GPU-minutes a day) |
JANCTION Render runs the same thing; the script only builds the scene, the camera and the frame range, and the service sets resolution, samples, denoising, device and output. The agent-facing flow is on the API page; a batch / CI angle is on headless Blender in the cloud.
| from | how |
| 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 / Enterprise | An 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) |
| ChatGPT | Plugins (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 Code | claude 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) |
| Codex | codex 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 Code | Add 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 CLI | agy 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 |
| OpenCode | Add https://render.janction.jp/mcp under mcp in ~/.config/opencode/opencode.json with "type": "remote", then opencode mcp auth janction-render (OAuth). Guide |
| Qwen Code | qwen 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 CLI | copilot 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 Chat | Add 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 |
| Manus | Connectors → 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 CLI | Kiro: "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 Studio | Tools → 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 Studio | Settings → 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 clients | Streamable 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 |
Can I run JANCTION Render's worker on my own GPU?
The worker is part of the operated service, not a product you install. If the farm must stay inside your network, the table above lists what to build; the public API shape is documented in the OpenAPI so a self-hosted clone can speak the same calls to the same agents.
Which Blender version is headless on the service?
A .blend opens with the version it was saved in (5.0, 5.2 or 5.3); scripts and 3D files use 5.0 unless you pass blender='5.2' or '5.3'. Scripts should target the 5.x Python API (materials always use nodes, keyframes via keyframe_insert). Blender 3.6, 4.2 and 4.5 are there too: pass blender='4.5' (or '4.2', '3.6'), and a script that stops on Blender 5 because it uses an older API is rendered again on 4.5, 4.2 or 3.6 automatically.
Does the API accept a script with imports like requests?
No. Network, subprocess and file access outside the job folder are rejected before the render (400 script_blocked) and audited at run time; bpy, math, mathutils, random and the standard geometry helpers are fine.
Is there a rate limit?
Yes, per key and per network: limited free GPU time (the welcome credit while it lasts, then up to 2 preview GPU-minutes a day), per-job frame and pixel limits, and request limits. The numbers are at /facts and in each error response.