The terms in full
Current authoritative terms, verified 2026-11-16. This page and /v1/pricing are generated from the same settings.
Connect in one line
MCP server: https://render.janction.jp/mcp. No sign-up. A welcome credit of up to 500 JPY for a new key (100 JPY with no card, 400 JPY more after saving a card that is not charged). Every other app: /blender-mcp.
| Claude.ai | Plugins (older menu: Customize → Connectors) → Add custom connector → https://render.janction.jp/mcp |
|---|
| ChatGPT | Plugins → Add → Create plugin → https://render.janction.jp/mcp |
|---|
| Claude Code | claude mcp add --transport http janction-render https://render.janction.jp/mcp |
|---|
| Claude Code on the web (claude.ai/code) | Plugins (older menu: Customize → Connectors) → Add custom connector → https://render.janction.jp/mcp (same as Claude.ai) |
|---|
| Codex | codex mcp add janction-render --url https://render.janction.jp/mcp |
|---|
| Cursor / VS Code / JetBrains / Kiro / LM Studio / Cherry Studio / others | Streamable HTTP at https://render.janction.jp/mcp (OAuth, or Authorization: Bearer <api key>) |
|---|
| Microsoft Copilot Studio | Tools → Add a tool → Model Context Protocol → https://render.janction.jp/mcp (OAuth dynamic discovery, or API key header X-API-Key) |
|---|
| Claude Desktop and stdio-only clients (npm) | npx -y janction-render (mcpServers: command npx, args [-y, janction-render]) |
|---|
| HTTP API | curl -X POST https://render.janction.jp/v1/keys for a key (no sign-up) |
|---|
Welcome credit
| Amount | 100 JPY (1,000 GPU-seconds) per new key, for previews and finals |
| Lasts | 14 days from key creation. The balance and expiry are in GET /v1/me under quota.welcome (MCP: billing) |
| One per network | One full welcome credit per network every 30 days; further keys from the same network use what is left of that network's credit |
| First top-up | The first top-up during the 14 days counts 1.5x, with the bonus capped at 500 JPY (100 JPY buys 150 JPY of credit) |
| Sign-up | None. POST /v1/keys returns a key; MCP clients get one through the OAuth consent page. No card for the first 100 JPY of the welcome credit |
| Saving a card | Saving a card on a Stripe page that charges nothing adds 400 JPY once per card (prepaid cards do not qualify). Offered only when the cardless credit is used up (card_offer on the 402, GET /v1/me and the MCP billing reply) |
Free and paid keys
Rendering bigger Blender files? Free keys send .blend files up to 1GB; paying 500 JPY or more in total opens .blend files up to 5GB, and your input files and render results are kept for 7 days instead of 24 hours. Saving a card alone does not unlock 5GB; it applies after an actual payment.
| Free | Paid |
| .blend upload | up to 1GB | up to 5GB |
| Other 3D files (GLB, FBX, USD and others) | up to 512MB on both |
| Data kept | 24 hours after last use | normally up to 7 days after last use |
| Scene storage on Render | up to 20GB per key in total (the input scenes still kept; assets have their own limit, render results are not counted) |
| Rendering | free credit and free daily previews | metered at 0.1 JPY per GPU-second |
| Start | no sign-up | pay 500 JPY or more in total (make a key at /start first; the monthly plans count the same) |
Every monthly plan (from Basic) sends .blend files up to 10GB (scene storage on Render up to 50GB per key, separate from JANCTION Storage (beta)).
A paid key is one that has paid 500 JPY or more in total (top-ups, auto top-up, monthly plans; the free credit, the card-saving credit and bonuses do not count). Once paid, a key keeps 5GB uploads and 7-day keeping even when its balance reaches 0. After a full refund or a chargeback, new use is treated as free; data already kept stays until the expiry it had then.
Data of paid users is normally kept for up to 7 days after last use. It may be kept for less when the operation requires it, for example when server storage runs short. Keep a copy of anything important.
The temporary link for a file left at /upload is separate from this: 12 hours. Download links for results last about 24 hours and can be renewed while the data is kept.
Start from your problem: what is really free · render without a GPU · cloud rendering, step by step
After that
| Previews | Free up to 2 GPU-minutes (120 GPU-seconds) per key per day, reset at 00:00 UTC (09:00 JST); beyond that, the same price as finals |
| Finals | 0.1 JPY per GPU-second (6 JPY per GPU-minute). A GPU-second is worker time including Blender start-up and scene load |
| Examples | 4-frame preview (about 4 GPU s) ≈ 0.4 JPY; 24-frame 720p MP4 (about 60 GPU s) ≈ 6 JPY; one 1080p frame at 128 samples (about 11 GPU s) ≈ 1.1 JPY (benchmarks). Each of these is 0 JPY while the welcome credit lasts |
| Per final render | Up to 3,000 frames per instruction (run as parts of 240 under one job id); 1080p per frame on free time, up to 4K (3840x2160) on prepaid credit; at most 10 GPU-hours per job (oversized jobs get 400 beta_limit) |
How you pay
| Credit | Prepaid credit bought by card at a Stripe Checkout page (from 100 JPY in steps of 100 JPY). A job needs only its estimate in credit (up to 1.5x is held when the balance allows), is settled at the actual GPU seconds and the difference is released |
| Failed jobs | Only the finished part counts. The unfinished part is not counted up to 5 minutes per key per day; failures on JANCTION's side never count |
| Without enough credit | HTTP 402 payment_required with checkout_url (the top-up page) and how much of the job the free time covers |
| Quote first | render_estimate / POST /v1/estimate returns GPU seconds, a wall-clock estimate, the free time left, the amount that would be charged (cost.estimated_yen), the currency and an expiry, so an agent can state the cost before running |
| Spend caps | No default cap (prepaid credit is the limit); each key can set a per-request and a per-day cap, and a request can carry max_yen. The cap set for a render request applies to the whole request, however the service splits it internally; change them with POST /v1/me/limits |
| Auto top-up | With a saved card, 2,000 JPY (2,000 JPY of credit) is added when the balance drops below 200 JPY. The amount, the threshold and the monthly cap can be changed (by default at most 10,000 JPY a month and 3 times a day). A job that would run short is topped up on the spot instead of stopping. Turn it on or off with POST /v1/billing/autocharge and POST /v1/billing/autocharge/off; over MCP, with the links billing returns |
| Monthly plans | Basic: 1,500 JPY a month adds 1,500 JPY of credit (about 9 1080p 240-frame animations); Standard: 4,500 JPY a month adds 4,500 JPY of credit (about 28 1080p 240-frame animations); Pro: 15,000 JPY a month adds 15,000 JPY of credit (about 93 1080p 240-frame animations) (a monthly top-up). Each month's credit resets at the next renewal (unused credit does not carry over) and the price per GPU-second is the same. Cancel anytime; it runs to the end of the paid month. Subscribe with POST /v1/billing/subscribe; list: GET /v1/billing/plans |
| Seller | JasmyLab Inc. (legal notice) |
Top-up amounts
| You pay | Credit you get | If it is your first top-up in the welcome period | About |
|---|
| 100 JPY | 100 JPY | 150 JPY | 0.3 GPU-hours |
| 500 JPY | 500 JPY | 750 JPY | 1.4 GPU-hours |
| 3,000 JPY | 3,000 JPY | 3,500 JPY | 8.3 GPU-hours |
| 10,000 JPY | 10,000 JPY | 10,500 JPY | 27.8 GPU-hours |
The first top-up in the 14-day welcome period counts 1.5x, with the bonus capped at 500 JPY. Any amount from 100 JPY can be paid. Bonus credit is not refundable in cash and is withdrawn in proportion if a top-up is refunded. Credit expires six months after the purchase.
Per-product prices and a five-minute start: Products.
Machine-readable
GET /v1/pricing returns the same information as JSON (view). Quotes: POST /v1/estimate.
Updated 2026-11-16.