Does the product need to be a .blend?
No. A GLB / glTF / FBX / USD / OBJ / STL / PLY link is imported into an empty scene, centered and framed. A .blend works too and keeps its own camera unless orbit=True.
Give the agent the product's 3D file (a GLB, glTF, FBX, USD or OBJ link, or a .blend) and ask for a turntable: on JANCTION Render that is one call, render_final(scene_url=..., orbit=True, orbit_frames=24, environment='studio', output='mp4'), and the agent gets back an MP4 of one full rotation with the camera framed on the object. A 24-frame 720p turntable of a headphones model took 58 GPU-seconds on the production GPU (about 6 JPY at 0.1 JPY per GPU-second, or nothing within the welcome credit). Preview the first four angles first (render_preview with orbit=True), fix the lighting or the framing, then render the final. No Blender, no GPU and no account are needed on your 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 a turntable of your modelBuild 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.
Real runs on the production GPU (NVIDIA RTX PRO 6000 Blackwell; the WaterBottle GLB is Khronos's public-domain sample):
| machine / route | settings | GPU seconds | cost | round trip |
|---|---|---|---|---|
| uvx janction-render turntable <link to WaterBottle.glb> (2026-10-10) | 24 frames, 1280x720, one full turn, MP4 | 85.2 GPU-s | about 8.5 JPY | — |
| HTTP API, orbit final (monkey + metal cube) | 48 frames, 960x540 / 24, MP4 | 75.7 GPU-s | about 7.6 JPY | 80 s |
| HTTP API, orbit preview (0/90/180/270 degrees in one image) | 4 angles, 320x180 tiles / 8 | 2.5 GPU-s | within the free previews | 7 s |
The turntable is a fixed-price outcome: the ceiling is shown before anything runs and only the GPU seconds used are charged.
Sources: /benchmarks (2026-09-30 to 2026-10-01), examples/one-command (2026-10-10), a laptop measured on 2026-10-11. Individual runs, not a guarantee; 0.1 JPY per GPU-second after the welcome credit.
render_final(scene_url="https://render.janction.jp/samples/ex21_product_clock.py", asset_urls=["polyhaven:alarm_clock_01"], preset="turntable", orbit_elevation=25, orbit_distance=0.85)
render_final(scene_url="https://render.janction.jp/samples/ex21_product_clock.py", asset_urls=["polyhaven:alarm_clock_01"], preset="product", orbit_elevation=25, orbit_distance=0.85)The script, settings and GPU seconds are on each example's page. Prices at 0.1 JPY per GPU-second; 0 while the free credit covers it.
One MP4 (24 fps) of a full rotation around the product, lit by a studio HDRI, with the camera distance and elevation chosen automatically from the model's bounds. Options: orbit_frames 24 / 48 / 96 (smoothness), orbit_elevation in degrees (default 18), transparent=True for WebM / GIF / WebP with alpha, environment studio / sunset / overcast / night. The measured example: headphones, 24 frames, 1280x720, 64 samples, 58.3 GPU-seconds.
render_preview(scene_url=..., orbit=True, environment='studio'): four angles in one image in a few seconds. Say what to change (lighting preset, elevation, background).render_final(scene_url=..., orbit=True, orbit_frames=24, width=1280, height=720, environment='studio', output='mp4'). The agent reports the time estimate and returns a download link (valid 24 hours), or a share page you can send to the client.curl -s -X POST https://render.janction.jp/v1/keys # a key, no sign-up
curl -s -X POST https://render.janction.jp/v1/files/url -H "X-API-Key: $KEY" \
-H "Content-Type: application/json" -d '{"url": "https://example.com/headphones.glb"}' # -> scene_id
curl -s -X POST https://render.janction.jp/v1/outcomes/turntable -H "X-API-Key: $KEY" \
-H "Content-Type: application/json" -d '{"scene_id": "...", "size": "720p", "frames": 24, "environment": "studio"}'
# -> job_id and a fixed price (0 within the welcome credit); then GET /v1/jobs/{job_id} until done and fetch output.mp4
POST /v1/outcomes/turntable is the fixed-price form of the same render (the price is stated before the job starts); POST /v1/jobs with orbit: true is the metered form. Both are in the OpenAPI.
curl -s -X POST https://render.janction.jp/v1/batches -H "X-API-Key: $KEY" -H "Content-Type: application/json" \
-d '{"outcome": "turntable", "defaults": {"size": "720p", "frames": 24},
"items": [{"ref": "sku-001", "scene_url": "https://example.com/a.glb"},
{"ref": "sku-002", "scene_url": "https://example.com/b.glb"}]}'
# -> 202 {"batch_id": "b_...", ...}; then GET /v1/batches/b_... shows each item's job and status
Up to 100 items per batch. Each item is fetched and submitted on its own, with the same quota and limits as single jobs; an item that fails gets its own error and the rest continue. POST /v1/batches/{batch_id}/retry submits only the failed items again (items that rendered are not drawn or charged twice). Add notify_url to get one POST per finished item.
| Good fit | Not this |
|---|---|
| catalog items as GLB / glTF / FBX / USD / OBJ; packshots for a product page; a batch of SKUs from a script | editing the model (use a modeling tool or a local Blender MCP first); photoreal cloth or fluid simulation |
| 24 to 96 frames; up to 1080p while covered by free time and up to 4K with prepaid credit | resolution above 4K |
Given as an https link, a glTF or OBJ brings the .bin and textures it references from the same folder as the file; a .gltf uploaded on its own needs them sent as assets, or the job is refused before it runs (a .glb needs nothing else); FBX and USD should embed or ship their textures (pass extra files with asset_urls). Transparent background: transparent=True with output='webm' (or gif / webp); MP4 cannot carry alpha. See rendering 3D files and turntables from a .blend.
| 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 |
No. A GLB / glTF / FBX / USD / OBJ / STL / PLY link is imported into an empty scene, centered and framed. A .blend works too and keeps its own camera unless orbit=True.
Yes: POST /v1/outcomes/product-shot (0 / 90 / 180 / 270 degrees, PNG, optional transparent background), or cameras=[...] for named cameras in a .blend.
Measured: 24 frames at 720p, 64 samples, 58 GPU-seconds plus a few seconds of queue. 48 frames roughly doubles it. The agent tells you the estimate before it starts.
Yes, under the current terms (see /terms). The service is provided as is with no availability guarantee; you own your renders.