Docs
Credits & limits
Credits are Apple's unit of daily energy. Every AI request burns some; your balance refills to full once a day, up to a monthly ceiling. The system exists for one reason: real inference costs real compute, and a hard, transparent quota is what lets the free tier be genuinely free — no card, no trial clock, no surprise bill.
The numbers
- Free plan: 231 Credits per day · 2,310 a month.
- Pro plan: 416 Credits per day · 12,600 a month.
- Max plan: 700 Credits per day · 21,000 a month.
- Each request: from 4 Credits.
Those are starting prices, not ceilings: a request settles against the compute it actually used, so a short question lands on its figure and a long build climbs past it. In practice the free allowance is a solid daily session — about 57 requests.
How metering works
Your balance is one click away in the workspace: the dock down the left edge carries a Usage and Credits row, and it opens a page with the figure, the last thirty days, and what your next request costs. The left navigation is closed when the workspace loads, so the meter itself is not on screen until you open it — once you do, it sits in the footer of the left rail beside your account, reading what is left, what your allowance is and when it resets. Either surface is read when the page loads and does not refresh itself while you build — reload for the current figure. What does move as it happens is the run you are watching: the thinking panel counts the Credits this run has spent, step by step. One Credit is taken when a request starts, and the rest settles against the compute the run actually consumed, so a long build's cost arrives as it is incurred rather than as a total you could not see coming.
A step that fails on our side is not charged: Credits are settled from the compute a call actually reported, and a call that returned nothing reports nothing. Beyond that, a run that ends in failure having left you nothing to keep gives its Credits back on its own — the reply tells you how many and you do not have to ask. A run that changed your place keeps its Credits whatever went wrong afterwards, because the work is still there; and stopping a run yourself is not a failure, so it is not refunded.
The daily reset — and the monthly ceiling behind it
Quotas reset at midnight UTC — one fixed instant for every account, not a rolling window that starts when you do. That is worth knowing if you build late in the UTC day: credits spent at 23:00 UTC are refilled an hour later. The workspace shows your exact reset time. Unused Credits do not roll over — every day starts at your full allowance.
There are two limits, and you have whichever is smaller. The daily figure is a rate; the monthly figure is a ceiling, and a day's refill cannot take you past it. On the Free plan the ceiling is the one that bites: 231 a day against 2,310 a month is 10 full days. Spend the whole daily allowance every day and the eleventh is where it stops until the month turns. Pace it and the same total stretches across the month instead. The usage meter names which of the two you are up against rather than showing one number for both.
Running out
When your balance hits zero:
- New AI requests are declined with a clear message and your reset time — never a silent failure.
- Everything that does not burn inference keeps working: reading chat history, browsing your project, creating and restoring checkpoints, pairing Studio.
- Nothing is deleted, downgraded or lost. You are just out of energy until the reset.
The limit that is not yours
Your allowance is not the only ceiling. Apple also caps what the whole service spends on inference in a day, shared by everyone using it, and that cap can be reached while your own balance still has Credits in it. A run stopped by it says so in its own words — “Apple has reached today's shared building capacity” — and it resets at midnight UTC like everything else here. It exists so that one runaway build cannot take the free tier down for the rest of the day. Troubleshooting covers what a run that hits it costs you and what it leaves behind.
Project files
Apple keeps notes, plans and generated data in a workspace beside each project — Apple's own storage, not your Roblox place — and you can open, add, rename and download those files from the Files drawer in the workspace. It holds text files only: .md, .txt, .json, .csv, .luau, .lua, .ts, .js, .yml and .yaml. Generated images are separate: download them from their result in the conversation. Roblox models live in your place.
- 48 KB per file. A file past that is refused rather than truncated, so a half-saved document is never what you find later. Long material belongs in several files.
- 20 earlier versions of each file are kept. Every write archives the one before it, and any kept version can be read and put back — putting one back is itself a new version, so nothing in between is lost.
- Deleted files are recoverable for 30 days. Delete moves a file to the project's trash with a real deadline on it, and the drawer says how long each one has left.
None of this counts against your Credits. Credits pay for inference; files are storage, and the storage has the limits described here.
Generated images
New generated images stay with their project until it is deleted. Each image can be up to 1 MiB, with at most 64 images and 16 MiB of encoded image data per project (encoding uses about a third more space than the downloaded file). Download a copy to keep outside Apple. Older temporary images that have expired cannot be recovered.
Generation is refused before starting when project or service storage is full. Existing images are not removed to make room. Concurrent runs can still fill the space while an image is being generated; if saving fails, Apple reports that failure instead of claiming delivery.
Other limits worth knowing
- Rate limiting: requests are queued per account, and under heavy load a request may briefly wait. No plan buys a place further up that queue — paying changes your allowance, not your turn.
- Checkpoints: Apple keeps your 25 most recent checkpoints per project. Taking the twenty-sixth deletes the oldest in the same write — by age, whether you took it yourself or Apple took it before a change. Restore the one you want before it falls off the end.
- One account per person: multiplying free accounts to farm quota is against the terms and gets caught.
Making Credits go further: give Apple specific requests (“the door in Workspace.Lobby”) rather than vague ones. Nothing else moves the number much — the expensive request is almost always the one that had to be sent twice.