Front page / Product shots from fixed camera angles, one job, no local GPU
Product shots from fixed camera angles, one job, no local GPU
Put one camera object per angle in the bpy script (for example Iso, Top, Front, Side, CloseA, CloseB, CloseC), then call render_preview(scene_script=..., cameras=['Iso','Top','Front','Side','CloseA','CloseB','CloseC'], environment='studio'): all seven come back tiled in one labeled image in about 5 GPU seconds. When it looks right, render_final with the same cameras list returns one 1080p PNG per camera (camera_files tells which is which). One job instead of seven; the preview sheet costs the same as a single 720p frame. 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.
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.
Measured, not estimated
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 shots <link to WaterBottle.glb> (2026-10-10)
4 PNGs at 0/90/180/270 degrees, 1920x1080, studio light, plain backdrop
13.9 GPU-s
about 1.4 JPY
—
HTTP API, orbit preview (the 4 angles in one image, to check framing first)
4 angles, 320x180 tiles / 8
2.5 GPU-s
within the free previews
7 s
uvx janction-render turntable <the same GLB> (2026-10-10)
24 frames, 1280x720, MP4
85.2 GPU-s
about 8.5 JPY
—
Product shots are 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.
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.
The prompt
Paste this into ChatGPT (with the JANCTION Render connector), Claude.ai, Claude Code or Cursor:
Build a Blender scene of a white ceramic mug on a light gray studio floor.
Add seven cameras named Iso, Top, Front, Side, CloseA (rim), CloseB (handle), CloseC (base).
Preview all seven with JANCTION Render in one sheet using cameras=[...] and environment='studio'.
Show me the sheet; when I say OK, render one 1920x1080 PNG per camera.
What the agent calls
render_preview(scene_script="...", cameras=["Iso","Top","Front","Side","CloseA","CloseB","CloseC"], environment="studio")
# -> one labeled sheet (3 columns), final_estimate and quota_left_today (free GPU time left: the welcome credit while it lasts, then up to 2 preview GPU-minutes a day)
render_final(scene_id="<from the preview>", cameras=["Iso","Top","Front","Side","CloseA","CloseB","CloseC"],
width=1920, height=1080, samples=128, environment="studio")
# -> frame_0001.png .. frame_0007.png; camera_files = {"Iso": "frame_0001.png", ...}
Each camera is a normal Blender camera object: cam = bpy.data.objects.new("Top", bpy.data.cameras.new("Top")), placed and aimed in the script. The service switches scene.camera between renders inside one Blender session, so the scene is loaded once.
Why one job
One upload and one Blender start instead of seven; the preview sheet costs the same GPU time as a single 720p frame.
Change a material or the background, preview again, and all seven angles update together.
The final returns one file per camera, named in order, so a catalog or a configurator can pick them up by camera name.
Backgrounds and lighting
environment='compare' on a single-camera preview shows studio / sunset / overcast / night in one image; pick one and pass it with the cameras list. environment_visible=false keeps the HDRI lighting on a flat gray backdrop; transparent=true with output="png" gives an alpha background for web pages.
Limits
Up to 8 cameras per job, one frame per camera (frame_start picks it). Not combinable with orbit, environment='compare' or a single camera. For an animation from several cameras, submit one job per camera.
Connect
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)
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
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
the 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
How do I batch-create ecommerce images from 3D models?
Use one product-shot request per model. Each request imports GLB, FBX, USD or OBJ, previews the framing, and returns four consistent PNG angles; use an Idempotency-Key per SKU and notify_url for the completion webhook. The price ceiling is returned before rendering.
Can I create white-background product photos from a 3D model?
Yes. Use POST /v1/outcomes/product-shot or the /start product-shots mode with a plain white backdrop. Preview the four angles first; choose transparent PNG instead when the marketplace adds its own background.
Does the preview sheet cost more with seven cameras?
No. The sheet is tiled into one 1280x720 image, so seven tiles cost about the same GPU time as one 720p frame, plus a few seconds of Blender start-up.
How do I know which PNG is which camera?
The job (and the MCP result) carries camera_files, a map from camera name to file name; frame_0001.png is the first camera in your list, and so on.
Can I render an animation from several cameras?
Not in one job: cameras renders one frame per camera. Submit one final per camera with frame_start..frame_end, or use orbit=true for a turntable.
Does it work from ChatGPT without any install?
Yes. Add the URL as a plugin in ChatGPT (Plugins → Add → Create plugin); the consent page creates a free key. No Blender and no GPU on your side.