What to check in Studio
Section titled “What to check in Studio”| Your check | Studio location |
|---|---|
Development allowance usage for debugKey requests | Account area → Billing → Studio plan |
| Runtime credit balance | Account area → Billing → Runtime credits |
| Project limits | Project → Settings → Budget & limits |
| Reports for your development requests | Project → Monitoring → Logs → Filters → Usage type → Development · Subscription |
Croche runs the model for you; production usage is charged to your project’s credit. Development allowance and Runtime credit are separate. Check the view that matches your app’s credentials. Event allowances are listed in the hackathon guide.
For a terminal view of project usage, use croche projects usage PROJECT_ID --period week; see the CLI guide.
Errors your app can receive
Section titled “Errors your app can receive”A turn can fail with a usage-related reason:
| Error code | Developer action |
|---|---|
development_allowance_exhausted | Check the development allowance in Studio before another development request |
project_budget_exhausted | Check the project’s Budget & limits before another request |
Keep the error’s code and message available in your app’s error handling. Show a useful failure state rather than leaving the UI waiting for a reply. Do not repeatedly send new requests to test whether a limit has cleared; review the relevant Studio setting first.