Front page / Render a 3D file (glTF, FBX, USD, OBJ, STL, PLY, Alembic) on a cloud GPU
Render a 3D file (glTF, FBX, USD, OBJ, STL, PLY, Alembic) on a cloud GPU
Upload the 3D file (or give an https URL) to JANCTION Render. It is imported into an empty Blender 5.0 scene (5.2 or 5.3 if you pass blender='5.2' or '5.3'), framed by an automatic camera, lit by a sun or an HDRI preset (environment='studio' and others), previewed in a few GPU seconds, and rendered as frames or an MP4; orbit=true gives a turntable. A .gltf or .obj given as an https link brings its .bin, .mtl and textures from the same URL folder; a .gltf uploaded on its own needs them sent as assets (a .glb is one file and needs nothing else). AI agents connect at https://render.janction.jp/mcp (remote MCP with OAuth; connecting creates a free key).
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.
What is supported
Turntable.orbit=true makes a camera circle the scene once (default 24 frames): a preview shows four angles, a final render gives the whole turn as an MP4. Handy for an imported model.
A 48-frame turntable (960x540, 24 samples, studio preset) made with render_final(orbit=true) from a bpy script: 76 GPU seconds on JANCTION Render, 2026-10-01.
Inputs: a .blend (send external images along, or pack them: File → External Data → Pack Resources), a bpy Python script
(no local Blender needed; set the scene, camera and frame range only, the service sets engine, resolution and samples), or a
3D file (glTF/GLB, FBX, USD, OBJ, STL, PLY, Alembic, imported into an empty scene). A scene without a camera or light gets an automatic
one and the response says so under warnings. environment = studio / sunset / overcast / night lights the scene with a bundled HDRI; a preview with environment="compare" shows the same frame under all four presets in one labeled image.
The same scene under the four presets. No lighting work in the script: pick one and the first render already looks finished (rendered by JANCTION Render, 2026-10-01).
From an agent (MCP)
render_preview(scene_url="https://example.com/models/chair.glb", environment="studio")
render_preview(scene_url="https://example.com/models/chair.glb", environment="compare") # 4 presets in one image
render_final(scene_id="<from the preview>", orbit=true, orbit_frames=48, width=1280, height=720, output="mp4")
Or let the agent find a model first: asset_search("wooden chair", kind="models") returns CC0 Poly Haven models; pass polyhaven:<id> in asset_urls.
curl -X POST https://render.janction.jp/v1/files -H "X-API-Key: $K" -F file=@chair.fbx
# textures for FBX / OBJ: POST /v1/files/{scene_id}/assets with the image files
curl -X POST https://render.janction.jp/v1/jobs -H "X-API-Key: $K" -H "Content-Type: application/json" \
-d '{"scene_id":"<id>","kind":"preview","frames":"1-4","environment":"studio"}'
What to expect
Scale and up-axis follow the importer defaults of Blender 5.0, or 5.2 / 5.3 with blender='5.2' or '5.3' (glTF Y-up is converted; FBX and OBJ use the file's units). If the model looks tiny or huge, the preview shows it and you can re-export with the right scale.
Materials: glTF PBR materials import fully; FBX and OBJ bring colors and image textures when the files are sent along; USD brings UsdPreviewSurface.
No camera in the file: an automatic camera frames all geometry (floors and walls are ignored when framing). orbit_target and orbit_distance adjust the shot.
Files are kept 24 hours after last use (7 days, normally, for keys that have paid 500 JPY or more in total), then deleted.
The 4-frame preview Claude.ai got from that prompt: 4 GPU seconds. The 24-frame 720p MP4 that followed took 58 GPU seconds (2026-10-01, RTX PRO 6000).
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.
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
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
Which 3D formats can be rendered without Blender?
glTF/GLB, FBX, USD/USDA/USDC/USDZ, OBJ, STL, PLY and Alembic are imported into an empty Blender 5.0 scene on the GPU server (5.2 or 5.3 if you pass blender='5.2' or '5.3'); nothing runs on your machine.
Do textures come along?
A .glb carries everything in one file. A .gltf or .obj given as an https link (scene_url) brings its .bin, .mtl and textures from the same URL folder, and the CLI sends the files next to it. A .gltf uploaded on its own (POST /v1/files or /upload) cannot: send its .bin and textures as assets under the same relative names (POST /v1/files/{id}/assets or asset_urls), otherwise a job on it is refused before anything runs, with no charge. A .gltf with everything embedded (data: URIs) works on its own. For FBX, send the image files as assets.
Can I get a turntable video of a model?
Yes: orbit=true on render_final (default 24 frames; set orbit_frames). A preview with orbit=true shows 0, 90, 180 and 270 degrees in one image.
Is there an API that renders an FBX from four angles?
Yes. Upload the FBX, preview it with orbit=true, then use POST /v1/outcomes/product-shot for PNGs at 0, 90, 180 and 270 degrees. The quote is returned before rendering; textures can be uploaded as assets.
Can I render a USD model from my browser?
Yes. Open /start, upload USD, USDA, USDC or USDZ, choose product shots or a turntable, and preview before the final. Blender and the GPU run on JANCTION; nothing is installed in the browser.