Unity AI Credits Budget Worksheet for Personal Plans - 2026

It is day four of the billing cycle. You still have a menu polish pass, two texture regenerations, and a “quick Agent fix” for the pause screen. By Thursday the dashboard shows 12 credits left and Generators are paused until the next reset. That is not a Unity bug. That is a missing Unity AI credits budget.
This is a business / spend worksheet for studios on Unity Personal who treat the $10/month / 1,000 credit allotment like a real line item - not another modes tutorial. Official allotment language lives on Unity AI features and Unity plans. Example burn ranges live in About Unity Credits. Mode safety (Ask → Plan → Agent order) stays in our companion post Unity AI Assistant Ask Plan Agent Modes - First Safe Session 2026. The MCP bridge cousin is Unity MCP with Cursor - First Safe Editor Bridge Session 2026 - MCP needs an AI subscription but does not spend Unity Credits per call.
Evidence note: Primary keyword unity ai credits. Demand signals include Semrush-tracked parent volume for unity and strong traffic on Unity’s Open Beta / MCP onboarding coverage. SERP gap: official tables list example costs; this URL adds a Personal-plan monthly worksheet, Ask / Plan / Agent / Generators caps, a Gateway BYOK escape, and a spend receipt - distinct from the safe-session modes walkthrough.
Non-repetition: This is not the Ask Plan Agent first safe session (mode order and Hierarchy verification). It is not the Unity MCP Cursor bridge (external tools allowlist). It is not the December engineering floor cap worksheet (founder hours). Same “cap the month” idea, different meter: credits, not calendar hours.
Why this matters now (July 2026)
Unity AI Open Beta for Unity 6 made Ask / Plan / Agent and Generators first-class inside the Editor. Personal users get a 14-day trial with 1,000 credits, then a $10/month subscription for 1,000 recurring credits (Unity AI FAQ, Open Beta thread). Credits do not roll over. When the balance hits zero, AI features pause until reset or you buy more.
What changed for micro-studios:
- Estimated costs are documented - Unity published example tables so teams can forecast before they click Run (credits docs).
- Agent nights are the silent killer - Lite Agent tasks can land in the tens; Ultra “simple” scenes can land near 150; advanced Ultra builds can approach 1,500 in a single thread.
- Generators compete with Assistant - Images are cheap per job (often 1–6), but four variations × five retries is still a week of Ask budget gone.
- SERP is pricing + docs - Review blogs restate the $10 figure. Indies still need a Monday spend ritual with hard caps.
Direct answer: Open the Unity Dashboard Manage Credits tab, record credits_remaining, fill the worksheet below so Ask + Plan + Agent + Generators + buffer ≤ 1,000 (or your actual allotment), latch gates C1–C6, and set unity_ai_credits_ok: true only when the month’s planned burn fits the remaining balance.
Who this worksheet is for
| Audience | Outcome |
|---|---|
| Creators / beginners | Trial vs paid allotment; dashboard balance check; stop-at-red rules |
| Developers | Mode and model caps; Generators slice; receipt JSON |
| Companies | Diligence language for $10/seat AI line item; who may buy top-ups |
| Search | Primary keyword: unity ai credits |
Time: about 45–60 minutes to fill the first month sheet; 10 minutes each Monday to re-check balance.
Prerequisites: Unity 6 project with Unity AI enabled (or trial); access to Unity Dashboard credit views; a copy of the Ask Plan Agent safe session if you have never run Agent safely.
Who should skip this sheet
- Teams on Pro / Enterprise / Industry with bundled higher allotments who already have finance-owned AI budgets - adapt the same tables, but start from your seat allowance (pricing).
- Anyone looking for how to click Ask / Plan / Agent - use the modes tutorial first.
- Classic ML-Agents / NavMesh work - that is not Unity Credits billing; see Unity AI Toolkit explained and toolkit not working help.
Allotment reality - trial, Personal, Pro
Use Unity’s published language as the source of truth; numbers below are the July 2026 Personal path studios ask about most.
| Plan path | Credits | Notes |
|---|---|---|
| Personal free trial | 1,000 one-time | Use within 14 days; then subscribe or stop (Unity AI) |
| Personal paid | 1,000 / month | $10/month; unused credits do not roll over |
| Pro (example) | 2,000 / month included | Bundled with paid seat; confirm on products for your org |
| Enterprise / Industry | Higher bundled allotments | Seat + org policy; still need a worksheet |
Beginner rule: Treat trial credits like a soft open - practice Ask and Plan, not a full Ultra city hub. Treat paid Personal as a hard monthly wallet.
Developer rule: Record allotment_type (trial | personal_monthly | pro_bundled | topup) in every receipt so finance can tell a burned trial from a burned subscription.
Official burn ranges you must respect
Unity’s own disclaimer: examples are representative, not guaranteed rates. Actual spend varies with project context, conversation length, mode, model, and output count (About Unity Credits). Still, planning without ranges is how months die on Tuesday.
Assistant message examples (Lite vs Default vs Ultra)
| Activity (from Unity examples) | Mode / tier | Rough credits |
|---|---|---|
| Short Unity question | Ask / Lite | ~4 |
| API lookup | Ask / Lite | ~5 |
| Concept / error explanation | Ask / Lite | ~13 |
| Feature approach plan | Plan / Lite | ~13 |
| System architecture brainstorm | Plan / Lite | ~25 |
| Detailed implementation plan | Plan / Lite | ~48 |
| Simple script / component | Agent / Lite | ~8 |
| Custom Editor tool | Agent / Lite | ~25 |
| Cross-project debug fix | Agent / Lite | ~35 |
| Full gameplay mechanic | Agent / Lite | ~58 |
| Complex refactor | Agent / Lite | 100+ |
| Cinema room scene (Default) | Default | ~50 |
| Third-person controller (Default) | Default | ~190 |
| Fantasy city hub (Default) | Default | ~520 |
| Cinema room (Ultra) | Ultra | ~150 |
| Third-person controller (Ultra) | Ultra | ~450 |
| Fantasy city hub (Ultra) | Ultra | ~1500 |
Generator examples (per job)
| Activity | Rough credits |
|---|---|
| Image (style / foundation / Gemini band) | ~1–6 |
| Texture | ~1–9 |
| 3D model | ~8–13 |
| Sound / music / TTS / motion / skybox / video | ~1–15 band |
Studio rule: Budget Agent Ultra and large Default builds as explicit line items. Never “see how it goes” on the last 200 credits of the month.
The Personal plan budget worksheet
Copy this into release-evidence/ai/unity-ai-credits-budget-YYYY-MM.md (or a shared Notion page). Fill numbers before the first Agent night of the cycle.
Header
| Field | Value |
|---|---|
| Org / project | |
| Billing cycle start | |
| Allotment type | trial / personal_monthly / pro_bundled / topup |
| Starting credits | |
| Dashboard URL checked | |
| Owner (who may buy top-ups) | |
| Soft stop % | 80% of allotment spent |
| Hard stop % | 95% of allotment spent |
Envelope (Personal default = 1000)
| Bucket | Cap (credits) | % of 1000 | Purpose |
|---|---|---|---|
| Ask | 150 | 15% | Docs, errors, “how do I…” |
| Plan | 200 | 20% | Reviewable plans before writes |
| Agent (Lite) | 300 | 30% | Named micro-actions only |
| Agent (Ultra / large Default) | 150 | 15% | Max one approved heavy job / month unless top-up |
| Generators | 150 | 15% | Image / texture / mesh / audio jobs |
| Buffer / surprise | 50 | 5% | Never schedule this deliberately |
| Total | 1000 | 100% | Must equal allotment |
If you are mid-cycle: replace 1000 with credits_remaining and scale percentages, or freeze Agent Ultra until reset.
Weekly drawdown (four-week Personal month)
| Week | Ask | Plan | Agent Lite | Ultra / heavy | Generators | Weekly total |
|---|---|---|---|---|---|---|
| W1 | 40 | 50 | 80 | 0 | 40 | 210 |
| W2 | 40 | 50 | 80 | 0 | 40 | 210 |
| W3 | 40 | 50 | 70 | 150 | 30 | 340 |
| W4 | 30 | 50 | 70 | 0 | 40 | 190 |
| Sum | 150 | 200 | 300 | 150 | 150 | 950 (+50 buffer) |
Creator tip: Put the one Ultra / heavy job in Week 3, not Week 1. Week 1 is for learning burn rates on your actual project size.
Daily stop-lights
| Signal | Rule |
|---|---|
| Green | Under weekly envelope; Ask/Plan preferred |
| Yellow | ≥80% of weekly bucket used - Agent Lite only with named ticket |
| Red | ≥95% of monthly allotment used - Ask only; Generators off; no Ultra |
Mode caps that survive contact with reality
Translate the envelope into session rules so Discord “just one more Agent” cannot override the sheet.
| Mode | Personal default cap | Session rule |
|---|---|---|
| Ask | 150 / month | Unlimited prompts until bucket empty; stay Lite |
| Plan | 200 / month | Reject plans > ~15 steps; rewrite smaller |
| Agent Lite | 300 / month | One named Hierarchy/file change per turn |
| Agent Ultra / heavy Default | 150 / month | Written lead approval; screenshot before/after |
| Generators | 150 / month | Cap retries at 2 per prompt; turn Generators off in dashboard if needed (Unity AI FAQ) |
Pair these with the safe session script so budget and Hierarchy discipline travel together.
Generators vs Assistant - same wallet, different failure mode
Assistant burns credits on conversation complexity. Generators burn on job count × per-job cost. Indies often starve Agent by regenerating the same icon twelve times.
Generators hygiene checklist:
- Lock style + prompt in a text file before the first job.
- Budget N jobs, not “until it looks right.”
- Prefer 1–2 variations, then human edit in external tools.
- Remember multi-output actions sum per job (credits docs).
- If art is the bottleneck, buy a top-up or use non-Unity generators - do not silently empty Assistant.
Decision table:
| Need | Prefer | Why |
|---|---|---|
| API / compile questions | Ask | Cheap; no project writes |
| Multi-step feature design | Plan | Reviewable; cheaper than Agent thrash |
| One Hierarchy change | Agent Lite | Bounded write |
| Whole scene from a paragraph | Defer or top-up Ultra | Can equal an entire Personal month |
| Icon / texture iteration | Generators with retry cap | Or external art tool |
Gateway / BYOK escape hatch (when credits are the wrong meter)
Unity MCP / Gateway paths let external agents talk to the Editor. Important billing nuance from our MCP safe session: MCP requires an active Unity AI subscription but does not spend Unity AI credits per call. That does not mean “free AI” - you still pay the model provider (Claude, Cursor plans, API keys) and you still need an allowlist.
Use the escape hatch when:
- Personal credits are Red and you still need Editor tooling.
- The work is read-only console / Hierarchy inspection via MCP.
- Finance prefers provider invoices over Unity credit top-ups.
Do not use the escape hatch to:
- Bypass Plan review with unrestricted write tools.
- Hide spend - track provider cost in the same receipt under
external_ai_usd. - Skip the Ask Plan Agent baseline if you have never run a safe in-editor session.
Gates C1–C6 (credit latch)
| Gate | Check | Fail action |
|---|---|---|
| C1 | Dashboard balance recorded (credits_before) |
Stop; open Manage Credits |
| C2 | Envelope filled; sum ≤ allotment / remaining | Rewrite caps |
| C3 | Soft stop (80%) and hard stop (95%) written | Add stop-lights |
| C4 | Ultra / heavy job listed or explicitly none |
Block Ultra until named |
| C5 | Generators retry cap + optional Generators-off setting noted | Cap or disable |
| C6 | Receipt JSON saved; unity_ai_credits_ok matches math |
Do not claim green |
Latch: unity_ai_credits_ok = C1 ∧ C2 ∧ C3 ∧ C4 ∧ C5 ∧ C6.
Receipt schema - unity_ai_credits_budget_receipt_v1.json
Store under release-evidence/ai/.
{
"schema": "unity_ai_credits_budget_receipt_v1",
"project": "your-game-slug",
"billing_cycle_start": "2026-07-01",
"allotment_type": "personal_monthly",
"allotment_credits": 1000,
"credits_before": 1000,
"credits_after_planned": 50,
"envelope": {
"ask": 150,
"plan": 200,
"agent_lite": 300,
"agent_ultra_or_heavy": 150,
"generators": 150,
"buffer": 50
},
"ultra_job": {
"approved": false,
"ticket": null,
"estimated_credits": 0
},
"generators_retry_cap": 2,
"soft_stop_pct": 80,
"hard_stop_pct": 95,
"external_ai_usd": 0,
"mcp_used_as_escape": false,
"gates": {
"C1": true,
"C2": true,
"C3": true,
"C4": true,
"C5": true,
"C6": true
},
"unity_ai_credits_ok": true,
"owner": "engineering-lead",
"notes": "Week 3 Ultra deferred; Generators slice reserved for capsule icons only."
}
Verification steps:
- Sum envelope buckets; must equal
allotment_credits(orcredits_beforeif mid-cycle resheet). - Confirm
credits_after_planned = credits_before - (sum of non-buffer planned spend)lands ≥ buffer. - If
ultra_job.approvedis true, estimated credits ≤agent_ultra_or_heavybucket. - Set
unity_ai_credits_okfalse if any gate is false - do not “round up.”
Worked examples (Personal 1000)
Example A - solo hobbyist, scripting week
| Bucket | Planned |
|---|---|
| Ask | 120 |
| Plan | 80 |
| Agent Lite | 200 |
| Ultra | 0 |
| Generators | 40 |
| Buffer | 560 unused → reallocate next week or leave as safety |
Outcome: Comfortable month; no top-up. Matches “one to two heavy edits per week” hobby patterns discussed in third-party 2026 Unity AI coding comparisons without inventing studio names.
Example B - jam week with one Ultra scene
| Bucket | Planned |
|---|---|
| Ask | 80 |
| Plan | 120 |
| Agent Lite | 150 |
| Ultra | 450 (third-person controller class job) |
| Generators | 100 |
| Buffer | 100 |
Math: 80+120+150+450+100 = 900; buffer 100. Fail C2 if Ultra estimate is 450 but Ultra bucket was only 150 - either raise Ultra bucket (cut Agent Lite / Generators) or reject Ultra and split the controller into three Lite Agent tickets.
Example C - art-heavy marketing week
| Bucket | Planned |
|---|---|
| Ask | 50 |
| Plan | 50 |
| Agent Lite | 100 |
| Ultra | 0 |
| Generators | 700 |
| Buffer | 100 |
Outcome: Valid only if Generators are the product this month. Turn Generators off again after the capsule set ships so Agent is not starved next week.
Company diligence language (copy for partners)
Use when a publisher or lead asks “what does Unity AI cost us?”
Unity Personal AI is budgeted as a $10/month / 1,000 credit line item per subscribed seat (trial: 1,000 credits / 14 days). Credits do not roll over. We maintain a written envelope (Ask / Plan / Agent / Generators / buffer), soft stop at 80% and hard stop at 95%, and file
unity_ai_credits_budget_receipt_v1.jsoneach cycle. Ultra / large Default jobs require named approval. Top-ups and external Gateway / BYOK spend are recorded separately. Official consumption examples: About Unity Credits.
Governance ownership:
| Role | Owns |
|---|---|
| Engineering lead | Envelope math; Ultra approvals |
| Producer / founder | Top-up purchase yes/no |
| Art lead | Generators retry policy |
| Security | Never-paste secrets into Assistant / MCP |
Common mistakes
- Starting the trial with Ultra city hubs - burns the educational window.
- Ignoring multi-output Generator jobs - four images = four jobs.
- Assuming MCP is “free Unity Credits” - subscription still required; provider bills elsewhere.
- No soft stop - discovering Red at 3am with a ship build open.
- One shared org without an owner - everyone Agent-spends; nobody reconciles.
- Confusing this sheet with mode safety - budget ≠ Hierarchy discipline; run both.
- Treating docs examples as invoices - always reconcile against Dashboard history.
- Buying top-ups without raising the envelope - spend returns tomorrow.
Monday ten-minute ritual
- Open Dashboard → Unity AI → Manage Credits.
- Write
credits_remaininginto the sheet. - If below hard-stop threshold, set Generators off and Agent Ultra to
none. - Schedule the week’s Ask/Plan/Agent tickets against remaining buckets.
- Update receipt
notes; commit to VCS with other release evidence.
Same spirit as the engineering floor cap ritual - different meter.
How this pairs with other GamineAI Unity AI pages
| Need | URL |
|---|---|
| First safe Ask → Plan → Agent night | Ask Plan Agent modes |
| Cursor / Claude bridge | Unity MCP with Cursor |
| Longer prototype loop | Unity AI prototype course |
| Classic toolkit breakage | Unity AI Toolkit not working |
| Stack shopping | Top AI tools for Unity developers 2026 |
Key takeaways
- Unity AI credits on Personal are a $10 / 1,000 / month wallet after a 14-day / 1,000 trial - unused credits do not roll over.
- Plan with Unity’s example burn tables, then verify against the Dashboard - examples are not invoices.
- Split the month into Ask / Plan / Agent Lite / Ultra / Generators / buffer so one Agent night cannot empty the allotment.
- Cap Ultra / heavy Default as a named line item; advanced Ultra jobs can approach an entire Personal month.
- Generators compete for the same wallet - cap retries and prefer locked prompts.
- MCP / Gateway can escape credit burn per call but still needs subscription + provider spend + allowlist.
- Latch C1–C6 and file
unity_ai_credits_budget_receipt_v1.jsonwithunity_ai_credits_ok. - Keep this worksheet distinct from the modes safe session - budget and safety are both required.
FAQ
How many Unity AI credits do Personal users get?
Unity documents a 14-day free trial with 1,000 credits, then a $10/month subscription for 1,000 credits per month for Personal Edition (Unity AI, Open Beta discussion). Confirm your org’s current allotment in the Dashboard.
Do unused Unity AI credits roll over?
No. Official credits documentation states unused credits do not roll over between billing cycles (About Unity Credits). Plan the month; do not bank “leftover” Agent nights.
How fast can Agent burn a Personal allotment?
Example tables show Lite Agent tasks from roughly 8 credits for a simple script up through 100+ for complex refactors, while Ultra advanced builds can approach ~1500 credits - more than one Personal month (credits docs). Treat Ultra as a scheduled purchase decision.
Should I use Ask, Plan, or Agent when credits are low?
Prefer Ask, then small Plan reviews. Freeze Agent Ultra and Generators at hard stop. Mode order details: Ask Plan Agent first safe session.
Does Unity MCP spend Unity AI credits?
MCP requires an active Unity AI subscription but, per our MCP bridge guide, does not spend Unity AI credits per call. Track provider/API cost separately in external_ai_usd.
Where do I see my remaining balance?
Unity’s AI FAQ points to the Unity Dashboard Manage Credits area under Unity AI (features page). Record the number before every heavy session.
Can I turn Generators off but keep Assistant?
Yes. Unity’s FAQ notes Generators can be turned off in dashboard settings while keeping the Assistant active (Unity AI). Use that when art iteration is emptying the Agent envelope.
Is this the same as the Unity AI Assistant modes tutorial?
No. Modes teach how to run a safe first session. This page teaches how to budget the month so that session (and the next twenty) fit the Personal wallet.
Conclusion
Unity AI credits are not infinite Editor magic - they are a metered wallet with published example burn rates and a hard Personal ceiling. Fill the envelope before the first Agent night, put Ultra behind a named approval, cap Generator retries, and file the receipt. When the Dashboard goes Red, switch to Ask-only or the MCP escape hatch with eyes open - not panic top-ups. Bookmark this worksheet next to the Ask Plan Agent safe session and treat both as ship hygiene.
Related reads
- Unity AI Assistant Ask Plan Agent Modes - First Safe Session 2026
- Unity MCP with Cursor - First Safe Editor Bridge Session 2026
- December Engineering Floor Cap Worksheet - Contractors Offline Holidays 2026
- Top AI Tools for Unity Developers 2026
- Unity AI Toolkit Explained for Beginners
- Unity AI Toolkit Not Working - Step-by-Step Fix Guide
- About Unity Credits (Official)
- Unity AI Features Overview (Official)