On JANCTION Render a 1080p Cycles still (128 samples) of a product or interior scene takes 6 to 10 GPU-seconds (0.6 to 1 JPY at 0.1 JPY per GPU-second), a 24-frame 720p turntable MP4 takes 58 GPU-seconds (about 6 JPY), and a one-minute 24 fps video lands between about 150 JPY (EEVEE, 720p) and about 1,440 JPY (Cycles, 1080p, 128 samples), estimated from the measured per-frame times below. Each new key starts with a welcome credit of up to 500 JPY (14 days), so stills and short clips cost nothing while it lasts; after that, previews stay free up to 2 GPU-minutes a day and finals cost 0.1 JPY per GPU-second (since 2026-10-08). 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. 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.
All rows are real renders on the production GPU (NVIDIA RTX PRO 6000 Blackwell, 96 GB), the same records as the benchmarks and examples. Price = GPU seconds × 0.1 JPY. Within the remaining welcome credit (up to 500 JPY per new key (100 JPY with no card, 400 JPY more after registering a card, which is not charged) for 14 days) the charge is 0; after it, previews are 0 up to 2 GPU-minutes a day.
| Render | Settings | GPU seconds | At 0.1 JPY per GPU-second |
| 4-frame preview (tiled sheet) | 640x360 tiles, 16 samples | 4.0 | 0.4 JPY |
| Still: extruded metal logo, sunset | 1920x1080, Cycles, 128 samples | 6.2 | 0.6 JPY |
| Still: living room from primitives | 1600x900, Cycles, 128 samples | 5.4 | 0.5 JPY |
| Still: office towers at night | 1920x1080, Cycles, 128 samples | 9.6 | 1.0 JPY |
| Still: glass bottle (caustics, glass) | 1440x1440, Cycles, 128 samples | 166.5 | 16.7 JPY |
| Turntable: headphones, 24 frames, MP4 | 1280x720, Cycles, 64 samples | 58.3 | 5.8 JPY |
| Clip: wave through 144 cubes, 48 frames, MP4 | 1280x720, EEVEE, 64 samples | 56.6 | 5.7 JPY |
| Clip: letters rising, 48 frames, MP4 | 1280x720, EEVEE, 64 samples | 45.9 | 4.6 JPY |
Your scene will differ: glass, volumes and high sample counts cost more (the bottle above is 20 times the logo). The honest way to know is to run render_estimate on your own scene, which answers from the same measurements. One instruction takes up to 3,000 frames (rendered as automatic internal parts under one job id), so a one-minute 24 fps video (1,440 frames) is a single instruction.
Units differ (GPU-hour, OctaneBench-hour, GHz-hour, node-hour), so the only like-for-like comparison is your own scene on each service. The farms above are built for large jobs on many nodes; JANCTION Render is built for an agent that previews, fixes and renders in minutes on datacenter GPUs. GPUs available right now: 3 (from /v1/health). The number updates itself when GPUs are added. See the comparison and pricing.
| 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 |
Is anything charged today?
Not within the welcome credit. Each new key starts with 100 JPY of free GPU time (no card) and 400 JPY more after saving a card that is not charged, up to 500 JPY (14 days); after that, previews stay free up to 2 GPU-minutes a day and finals cost 0.1 JPY per GPU-second. Paid use started on 2026-10-08. 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.
How do I get a number for my own scene?
Call render_estimate (MCP) or POST /v1/estimate (HTTP) with the same body as the render. It returns GPU seconds, a sentence, and whether it fits the free GPU time left (the welcome credit while it lasts, then up to 2 preview GPU-minutes a day).
Why is the bottle 20 times the logo?
Glass with refraction and caustics needs far more samples per pixel to converge; the logo is opaque metal under an HDRI. Sample count, resolution and materials drive the time, not the frame count alone.
Does EEVEE always cost less?
For clips of a few dozen frames or more, yes: about two-thirds of Cycles per frame (same scene, 720p, 120 frames: 142 vs 223 GPU-seconds, 2026-11-06). Each EEVEE job pays about 7 seconds of shader compilation, so single stills and previews stay on Cycles.