Usage

Usage per environment and in total over a time range. Hosts report cumulative CPU, VMM memory, disk and egress bytes, and the control plane records hourly increments; browser_hours is computed from browser lease durations. The range defaults to this month (start of the month, UTC) through now; from must be earlier than to, otherwise 400. With environment_id, only that environment is shown (someone else's or a nonexistent one gives 404). Environments with no usage records in the range do not appear in data.

All monthly limits (developer-level ones first), with how much has been used this month (UTC).

Without environment_id the limit is developer-level (the total across all environments); with it, the limit applies to that environment. Setting the same (environment, metric) again replaces it. A limit is exceeded when this month's usage is greater than or equal to it: an environment over its limit is suspended within a minute (limits are checked again immediately after a change), over_limit states the reason, a limit_exceeded event is recorded and an environment.limit_exceeded webhook is sent; from then on resume, wake and exec return 409 limit_exceeded until the limit is raised or deleted, or the next month begins. When a developer-level limit is exceeded, every environment that has not been destroyed is suspended. A monthly_limit of 0 means nothing is allowed at all (suspended immediately). An unknown metric or a negative monthly_limit gives 400; an environment that is not yours gives 404.

Without environment_id, deletes the developer-level limit. 404 if there is no such limit. Limits are rechecked immediately after deletion, and environments suspended because of it can be woken again.