Billing
Understand your plan, billing units, and usage limits
Use the Billing tab to manage your plan and billing preferences. For month-to-date consumption, projected Answers spend, testing tasks, and limits, see Usage.
Usage model for your workspace
AirOps supports two usage models while workspaces transition between plans:
Combined task billing
Workflows, Playbooks, and Insights Answers draw from the same monthly task balance. Answers appear as tasks in Usage.
Legacy Answer Credits
Workflows and Playbooks use tasks, while Insights Answers are metered against a separate Answer Credit balance.
A workspace stays on its current model until its plan transitions, commonly at renewal or through another change agreed with the account team. Because timing can differ by workspace, the units and balances shown in Usage and Billing are the source of truth for your plan.
Setting Workspace Task Limits
You can set soft and hard limits on your workspace executions:
Soft Limit: receive an email notification when you reach the task threshold you set.
Hard Limit: prevent users from executing Workflows and Playbooks beyond the task threshold you set.
Configure limits under Usage → Limits. How Answers interact with those limits depends on your usage model and whether Protect Answers Tracking is enabled. For additional information about plans, visit the Pricing Page.
AEO Answers usage and billing
Every prompt you track in Insights is run daily across AI platforms, and each run produces an Answer that AirOps captures and analyzes. The amount of usage is the same under both models; the billing unit differs:
Under combined task billing, each Answer debits tasks from the shared monthly task balance.
Under the legacy model, each Answer debits the separate Answer Credit balance.
How Answers Are Calculated
A single tracked prompt does not produce one Answer. AirOps re-runs each prompt across every platform, region, and persona you have configured, so usage scales with your tracking setup.
For each tracked prompt, the monthly Answers are:
Where:
Platforms are the AI engines the prompt is assigned to (ChatGPT, Gemini, Perplexity, Google AI Mode, Google AI Overview, Claude).
Regions are the countries you track the prompt in, set under your Brand Kit's Insight Settings.
Named personas are the custom personas you define. The
1represents the default persona, which is always included unless you deselect it for a prompt.30 days reflects daily monitoring across a month.
Google AI Overview ignores personas. It always runs once per region per day, regardless of how many personas you have configured.
For example, a prompt tracked on ChatGPT, Gemini, and Perplexity, in the United States and the United Kingdom, with the default persona plus two named personas:
Provider multipliers
Most platforms debit one billing unit per Answer. In a combined-task workspace, that unit is a task. In a legacy workspace, it is an Answer Credit.
ChatGPT, Gemini, Perplexity, Google AI Mode, Google AI Overview
1
Claude
4
Claude Answers debit four times as many units as a standard provider.
How Answers affect your balance
In a combined-task workspace, Answer usage shares the same monthly task balance as Workflows and Playbooks. The provider multiplier above is included when AirOps calculates the task debit and projected Answer spend.
In a legacy workspace, Answer usage debits the separate Answer Credit balance. It does not draw from the Workflow and Playbook task balance until the workspace moves to combined task billing.
See Usage to review current and projected Answer spend. Combined-task workspaces can also use Protect Answers Tracking to reserve the projected tasks required for monitoring.
Frequently Asked Questions
What happens when I reach my included usage?
The behavior depends on your plan, usage model, limits, and overage terms. A hard task limit can pause Workflow and Playbook executions. In combined-task workspaces, Protect Answers Tracking can reserve tasks so monitoring continues when other executions pause. Check Usage → Limits and the Billing tab for the settings and balances that apply to your workspace, or contact your account team about plan-specific terms.
If a Workflow errors, will I still be charged for tasks?
You will only be charged tasks for steps within your Workflow that run successfully. Steps that error out will not be charged, but if you have other Workflows embedded in your Workflow that incur tasks, you will be charged for those.
How can I track my task usage?
Use the Usage tab to review pacing against your monthly allocation, resource-level consumption, Answers usage, testing tasks, and limits.
How can I test without using production tasks?
Workflow tests and Playbook runs started from the editor use testing tasks first. See Testing tasks for the current allowance and fallback behavior.
For Workflow task usage, refer to these parameters:
Text input step - no task usage incurred
Code step - maximum 1 task per Workflow run
Vector DB call - 1 task per call
LLM step with your own API key - 1 task per call
LLM step with an AirOps hosted model - tasks proportional to usage
Other API step - 1 task per call
Output step - no task usage incurred
Last updated
Was this helpful?