> For the complete documentation index, see [llms.txt](https://docs.airops.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.airops.com/your-workspace/settings/usage.md). # Usage The **Usage** tab is the central place to understand how your workspace is consuming its plan. Use it to review production tasks, testing tasks, Insights Answers, projected Answer spend, and usage limits. {% hint style="info" %} The units you see depend on your plan. Combined-task workspaces meter Workflows, Playbooks, and Answers in tasks. Workspaces on the legacy model show a separate Answer Credit balance for Insights. See [Billing](/your-workspace/settings/billing.md#usage-model-for-your-workspace) for details. {% endhint %} ## Monthly overview Start with the current billing period to compare usage with your included allocation. The overview brings together: * Production tasks used by Workflows and Playbooks * Answers usage and projected spend for the billing period * Testing tasks used while building and iterating * Soft and hard task limits Use the date controls when you need to investigate a shorter period or compare recent usage patterns. ## Workflow and Playbook usage The production usage breakdown shows where tasks are being consumed across Workflows and Playbooks. Use it to: * Compare total tasks used by each resource. * Review run volume and average tasks per run. * Identify resources responsible for a large share of workspace usage. * Find unexpected increases before changing a limit or plan. Task cost depends on the steps and models that execute. For example, a Workflow step that never runs does not incur usage, while an executed hosted-model step consumes tasks in proportion to its usage. See [Billing](/your-workspace/settings/billing.md#if-a-workflow-errors-will-i-still-be-charged-for-tasks) for Workflow charging behavior. ## Answers usage The Answers area shows how much of your Insights monitoring allocation has been used and the projected spend for the rest of the billing period. Review the projection before adding prompts, platforms, regions, or personas, because each additional tracking dimension increases the number of Answers AirOps collects. * In a **combined-task workspace**, actual and projected Answers usage is shown in tasks and draws from the same balance as Workflows and Playbooks. * In a **legacy workspace**, Answers are shown in Answer Credits and use a separate balance. Provider multipliers are included in usage and projections. Most providers consume one unit per Answer; Claude consumes four. See [AEO Answers usage and billing](/your-workspace/settings/billing.md#aeo-answers-usage-and-billing) for the calculation. ## Testing tasks Workflow tests and Playbook runs started from their editors use the workspace's separate testing task balance first. Each workspace includes 50,000 testing tasks per month for iteration. After that balance is depleted, additional editor runs use production tasks. Review testing usage separately from production usage so frequent iteration does not look like a production spike. For instructions on testing a Workflow, see [Testing and Iteration](/actions/workflow-concepts/testing-and-iteration.md). ## Limits Open **Usage → Limits** to manage guardrails for production tasks: * **Soft limit:** sends an email notification when usage reaches the threshold you set. * **Hard limit:** prevents users from running additional Workflows and Playbooks when usage reaches the threshold you set. Only workspace Admins can change usage limits. Revisit them when projected Answers spend or production run volume changes materially. ## Protect Answers Tracking **Protect Answers Tracking** helps combined-task workspaces keep daily Insights monitoring active as the shared task balance approaches its limit. It appears under **Usage → Limits** and is marked **Recommended**. When it is enabled: * AirOps reserves the tasks projected to be required for Answers tracking through the end of the billing period. * Workflow and Playbook runs pause at the workspace limit before they consume the reserved Answers tasks. * The setting shows the number and percentage of included tasks currently reserved. When it is disabled, Answers compete with Workflows and Playbooks for the same task balance. Monitoring can stop if that balance is exhausted. {% hint style="info" %} Protect Answers Tracking applies to combined-task workspaces. Workspaces using legacy Answer Credits manage Answers against their separate credit balance. {% endhint %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.airops.com/your-workspace/settings/usage.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.