Usage connects consumption to the resource and service responsible for it. The owning Workspace pays for authorized work, including work performed by collaborators and production activity on its Sites.
A short response can still consume credits if it invokes a model or paid service. A quiet conversation also does not mean an associated production destination has stopped running.
Read the categories
| Category | Investigation |
|---|---|
| Compute | Allocated Sandbox and production runtime activity |
| Inference | Model calls, text or media generation, and task volume |
| Services | Remote Browser sessions, web operations, and supported service ingestion |
| Storage | Retained capacity, applicable transfer, and extended retention |
Credits express billed consumption. Raw tokens, seconds, bytes, and request counts measure different things and should not be added together as though they were equivalent charges.
Investigate a change
- Select the relevant Workspace and reporting period.
- Identify the resource and service category responsible.
- Check the work, release, or runtime activity in that period.
- Distinguish included consumption from billed excess where applicable.
- Review any ongoing work before changing future limits.
Customer-funded providers can charge upstream consumption directly. Playbooks may still meter the orchestration, runtime, or other platform work it supplies. Check both sides when an external provider is selected.
Viewing and creation differ
Ordinary private opening and browser-local interaction with a retained Artifact have no dedicated Compute session or per-open fee within platform limits. Creating, revising, or preparing the experience can consume Inference, Compute, or Services. Retained bytes and transfer follow their applicable Storage rules.
Opening the viewer does not start a paid remote Browser session. A Site, an Artifact viewer, and an application development preview also have different operational models.
Use Budgets to control future admission and Credits to inspect funding. Usage already incurred is not erased by reducing a budget.
Example: separate creation from viewing
Creating an interactive calculator can use models and execution services. Opening its retained Artifact later in the browser is a different activity from asking the Operator to revise it or running a production application.
When consumption changes, identify which activity occurred before comparing totals. Artifacts, Browser, and Site Runtime explain those execution models.
Compare like periods
Compare the same Workspace, resource, and reporting interval when evaluating a change. Note whether the interval includes a new Site, a recurring task, or retained Storage. If costs continue after editing stops, inspect those ongoing resources instead of attributing everything to the last Operator response.