Can we get an invoice now?
Not yet. Credit is bought by card at a Stripe Checkout page. For a receipt for a top-up, ask through the support page.
Yes, a company can use JANCTION Render today: it is operated by JasmyLab Inc. (Tokyo) and provided as is without an availability guarantee, with no sign-up (a key per person or per pipeline), spend caps per key, and inputs and results deleted 24 hours after last use (7 days, normally, for keys that have paid 500 JPY or more in total) and never used for training. Each new key starts 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) (14 days); after that, previews stay free up to 2 GPU-minutes a day and finals are paid by card from prepaid credit (0.1 JPY per GPU-second, since 2026-10-08); there are no invoices yet. Commercial use of renders is allowed under the current terms. An independent security test of the public API, the MCP endpoint and the OAuth flow was run in October 2026 and its findings fixed; every render runs in an isolated, throw-away environment. There is no sales team: the service is self-serve, and questions go to the support page. 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 your own file for freeBuild 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.
| Question | Answer |
|---|---|
| Who operates it | JasmyLab Inc., Tokyo (legal notice) |
| Terms | terms: provided as is, no availability guarantee, no SLA; you own your renders |
| Where the data goes | scenes and renders are stored on the service's servers in Japan for the job and deleted 24 hours after last use (7 days, normally, for keys that have paid 500 JPY or more in total); share pages keep a copy only if you create one; privacy |
| Training | inputs and results are never used to train models |
| Accounts | none: a key per person or pipeline (POST /v1/keys or the OAuth consent page); keys can be revoked; spend and daily caps per key (POST /v1/me/limits) |
| Security | independent black-box test of the API, MCP and OAuth in October 2026, findings fixed; every render runs in an isolated, throw-away environment with no network access; security |
| Invoices | not yet. Credit is bought by card at a Stripe Checkout page. For a receipt for a top-up, ask through the support page |
| Support | support page |
| Status | status, /v1/health, What's New |
Each new key starts with a welcome credit of up to 500 JPY (14 days). Metered use is 0.1 JPY per GPU-second after the welcome credit (since 2026-10-08); previews stay free up to 2 GPU-minutes a day, and up to 3,000 frames per instruction (automatically split internally), 1080p on free time and 4K on prepaid credit. Credit is bought by card from 100 JPY. Details and the current state are on pricing and products.
POST https://render.janction.jp/v1/keys or the OAuth consent page of the MCP client. Keep keys in a secret store.POST /v1/me/limits with a per-job and per-day budget, so an agent cannot overspend. Set a spending cap for each render request: internal job splitting never increases that cap.notify_url instead of polling and Idempotency-Key on job submissions so retries do not double-render.https://render.janction.jp/mcp; the tool descriptions tell them when to use the service and when a local render is faster.What this is not: a managed studio pipeline, a many-node farm for long sequences, or a service with a sales team and custom contracts (see the large farms for that). It is a render tool for agents and scripts that a team can adopt in an afternoon.
| 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 |
Not yet. Credit is bought by card at a Stripe Checkout page. For a receipt for a top-up, ask through the support page.
Better not: a key is the unit of quota, caps and revocation. Make one per person or per pipeline.
In a datacenter in Japan operated for JasmyLab. Scenes and renders stay there for the job and are deleted 24 hours after last use (7 days, normally, for keys that have paid 500 JPY or more in total). Every monthly plan includes JANCTION Storage (beta): renders and scenes are kept for as long as you are subscribed (Basic 200 GiB, Standard 1 TiB for 3 people, Pro 5 TiB for 5 people). .blend uploads go up to 10 GB.
No. The service is provided as is; a GPU can be shared with other work, and jobs queue when every available GPU is busy (the tools report the expected wait).
Use the support page. There is no sales team; questions are answered there.