Billing & Usage for AI Agents

🔒
Who can see this page?
Billing & Usage is visible only to users with the Manage Agency Settings permission toggle enabled for their assigned User Role.

The page has three tabs: AI Usage, AI Billing, and Daily Limits.

AI Usage Tab

The AI Usage tab is the landing page under Billing & Usage. It shows you the actual activity happening across your agents — measured in raw tokens and actions.

Here's what you'll find:

Category	What it measures	Segment / breakdown options
AI Tokens	Tokens consumed by LLM models processing your agents' requests (prompt + completion tokens). Every model has its own rate per token.	• By Provider (e.g. Anthropic, OpenAI, Google) • By Model (e.g. Claude Sonnet vs. Claude Opus) • By Token Type (Prompt vs. Completion) • By Product (Agents vs. Data Apps)
AI Actions	Non-chat agent activity — generally tool use, such as web scrapes, image generation, web research, and more.	• By Action (image_generator, web_scraper, google_web_search, researcher, query_executor, browser_use, image_editor, video_generator) • By Product (Agents vs. Data Apps)
Data Compute	Data warehouse compute consumed when your agents query and process data.	Additional breakdowns coming soon

Understanding the Top Usage Table

There are two ways to slice the token and action data in this table:

Top Usage by Agent — token consumption and actions broken down by Agent Name
- Any built Agent that has consumed tokens will populate here based on the date range selected
- "Bob" refers to the Agent Builder Bob and its token consumption
- "Appy" refers to the Data App Builder and its token consumption
- "Other" was capturing token consumption for tokens that were not being attributed to an Agent prior to June 2nd. Changes were made on that date so that all tokens are now being attributed to an Agent, but those changes could not be made retroactively. When viewing data after June 2nd, you will not see an "Other" line.
Top Usage by User — token consumption and actions broken down by User
- "Other" captures tokens that weren't executed directly by a human user. This includes scheduled and webhook triggers — set up by a human user initially, but then initiated automatically later according to the trigger's rules — and when an agent is calling on a subagent

AI Billing Tab

The three credit categories in the AI Billing tab map directly to the three categories of raw usage tracked in the AI Usage tab:

AI Usage (raw)		AI Billing (credits)
AI Tokens	→	AI Token Credits
AI Actions	→	AI Action Credits
Data Compute	→	Data Compute Credits

The AI Billing tab translates that activity into credits so you can manage your plan. Your plan that you have with NinjaCat is based on these credits. In order to use our Agents and Data Apps features, there needs to be available credits.

This tab shows:

Remaining credit balance out of your total number of credits purchased
Estimated days remaining
- This estimate looks at your credit usage over the past 90 days, giving more weight to recent activity and accounting for whether usage is trending up or down. We project that pattern forward to estimate when your remaining credits would run out.
- The headline number reflects your typical usage rate. The listed range of days shows how the estimate shifts if usage runs higher than usual (the low end) or lower (the high end). When usage varies a lot, your typical rate can last beyond a year (365+) while a busier-than-usual stretch could still use credits sooner.
Estimated depletion date — the day your credits are projected to run out based on the above information
Credit category breakdown — how your credits are being spent across Token, Action, and Data Compute credits
Credit transaction history — credits purchased, credits spent per day, and end-of-day balance

Use this tab when you want to answer "How much have we spent and how long will our credits last?"

Avoiding a lapse in access when credits run low

When credits run out, agent requests will start to fail. To avoid that:

Reach out to your NinjaCat account manager or customer success manager to purchase additional credits.
Set a daily credit limit (requires the Manage Agency Settings permission). This caps how much of your overall plan can be burned in a single day, which protects you from accidentally draining your full balance in one busy day. See the Daily Limits Tab for how to configure this at the org, agent, and user level.
Watch the estimated days remaining and depletion date on the AI Billing tab — these update based on your actual burn rate and give you early warning.

Daily Limits Tab

The Daily Limits tab is the third tab under Billing & Usage (alongside AI Usage and AI Billing). It lets you cap how many credits your organization can spend in a single day, and optionally distribute that daily budget across individual agents and users. It gives you three layers of control, from broadest to most granular:

Level	What it controls	Required?
Org-Level	The overall ceiling on credits your whole organization can spend in a day.	Base layer
Agent-Level	How that daily budget is divided among your AI Agents.	Optional
User-Level	How that daily budget is divided among your Users.	Optional

Agent-Level and User-Level controls layer on top of the Org-Level limit — they never raise the org ceiling, they only divide it up further.

ℹ️
Daily Limits apply to AI Token and AI Action credits only
The limits you configure here do not include Data Compute credits. Data Compute credits (the data-warehouse compute tracked on the AI Billing tab) are not counted against your Daily Limits. Daily Limits govern the credits spent on agent token consumption and agent actions.

Org-Level Control

This is the highest level of credit control and sets the daily spending ceiling for your entire organization.

Global Daily Limit — the default number of credits that can be spent in a single day. This applies every day unless you override it.
Today's Active Limit — a one-day override of the Global Daily Limit that applies only to the current day. For example, if you've hit your Global Daily Limit and need more headroom just for today, you can raise Today's Active Limit (for example, from 1M to 2M credits). At the start of the next day it automatically reverts to the Global Daily Limit.

Agent-Level Control

An optional layer on top of the Org-Level Control that governs how much of the daily budget each AI Agent may consume.

Set a default allocation that applies to all agents, expressed either as a number of credits or as a percentage of the org-level daily limit.
Override the default for individual agents as needed.

Example: Set the default for all agents to a maximum of 5% of the daily budget, then override specific agents — allow the "Negative Nancy" agent up to 40%, and restrict the "Blog Writer" agent to 0%. You can define these allocations by percentage or by a fixed number of credits.

User-Level Control

An optional layer on top of the Org-Level Control that governs how much of the daily budget each User may consume.

Set a default allocation that applies to all users, expressed either as a number of credits or as a percentage of the org-level daily limit.
Override the default for individual users as needed.

Example: Set the default for all users to a maximum of 5% of the daily budget, then override specific people — allow Brian Lee and Paul Dereval up to 40% each. As with agents, you can define these allocations by percentage or by a fixed number of credits.

What happens when a limit is hit

When any of these limits — org, agent, or user — is reached, NinjaCat surfaces an error to the user identifying which specific limit was hit (org-level, the specific agent, or the specific user). Usage is blocked until the relevant credit budget is increased. To resume usage, raise the daily limit for the affected user, agent, or the organization as a whole.

When limits reset

Daily Limits reset at the start of each day in your organization's timezone, as configured in NinjaCat Organization Settings. (This is not a fixed midnight UTC — it follows whatever timezone your org has set.) At reset, Today's Active Limit reverts to the Global Daily Limit.

Who can manage Daily Limits

Anyone whose User Role has the Manage Agency Settings permission toggled on can access the Daily Limits dashboard and configure limits at the org, agent, and user levels.

Credit Definitions

NinjaCat uses a single credit currency:

100 credits = $1.00 (1 credit = $0.01)

There is no fixed credit-to-token ratio — the exact cost depends on the model, provider, and action being used. Credits are grouped into three categories:

Category	What it covers
AI Token Credits	Credits consumed by LLM models processing your agents' requests (prompt + completion tokens). Every model has its own rate per token. A single agent run will typically draw from both the AI Token Credits and AI Action Credits buckets, as it typically includes chat-based 'thinking' time + some variation of tool calls.
AI Action Credits	Anything that's non-chat agent activity — generally tool use. This covers the built-in tools an agent uses, such as web scraping, image generation, web research, and data queries. The following built-in tools count as AI Actions and generate AI Action Credits: • Image Generator (`image_generator`) • Image Editor (`image_editor`) • Video Generator (`video_generator`) • Web Scraper (`web_scraper`) • Google Web Search (`google_web_search`) • Researcher (`researcher`) • Query Executor (`query_executor`) • Browser Use (`browser_use`) Custom Actions and MCP Server Tools are not included in this category. Different actions are priced differently — some charge per invocation, some by browser time, some by units consumed (like Snowflake credits). It all gets converted to dollars and then to NinjaCat credits at the standard 100-credits-per-dollar rate.
Data Compute Credits	Credits consumed by data warehouse compute when your agents query and process data.

A few things worth knowing

Builder Bob (NinjaCat's in-platform agent builder assistant) shows up in Top Usage by Agent and does count against your token usage.
Data Apps are included in credit consumption and shown as a separate line item.
The AI Insights Widget in reporting is not part of AI credit pricing — it's covered under your reporting package.