Skip to main content
Credits are the unit of usage on Ruby. Every AI interaction (sending a message, running an agent, using a tool) consumes credits. This page explains what credits are, how they’re calculated, and when usage is free.

What is a credit?

A credit represents a unit of AI work performed on Ruby. Credits are consumed whenever you interact with agents, use tools, or run automated workflows. Credits are not transferable between users, do not roll over to the next billing period, and are not refundable.

How credits are calculated

Each interaction consumes credits based on two components that are added together: total credits = token credits + action credits

Token credits

Token credits are proportional to the amount of AI processing involved in generating a response. More complex queries, longer contexts, and more capable models consume more token credits.

Action credits

Action credits are a fixed amount charged per tool action, regardless of response length. Tools are grouped into 3 tiers:

Sub-agent costs

When an agent runs sub-agents in the background, each sub-agent’s credit cost is added to the total. Costs accumulate across the full agent chain and are displayed alongside the main agent cost.

Credit spend checkpoints

To prevent a long-running task from using excessive credits, Ruby pauses a root task started in the web app or browser extension when its cumulative AI processing spend reaches 600 credits. AI processing spend from sub-agents in the same task counts toward the checkpoint; fixed tool action credits do not. Sub-agent messages and tasks started from other origins do not pause at this checkpoint. The person who started the task can choose Yes, continue to resume it or No, stop to cancel it. Other viewers must wait for that person to decide. After a task is continued, it does not pause at the same checkpoint again. The checkpoint is on by default. Admins can turn it off for the workspace under Admin > Credits, Settings tab, with the Credit spend checkpoint toggle. The 600-credit threshold is fixed. Admins and managers can exempt individual agents with Ignore credit spend threshold alert in the Agent Builder’s Cost Management settings. See Credit management.

When credits are not consumed

Some interactions are exempt from credit consumption:
  • Sidekick: all Sidekick interactions (Tokens and Actions) are free and do not consume credits.

Credit cost display

After each message, Ruby shows the credit cost of that interaction directly in the conversation. This lets every member track their usage in real time without navigating to the Credits page. The conversation breakdown can also be viewed By tools, By models, or By agents. The display includes the cost of the main agent response and any sub-agents that ran in the background as part of that interaction.

Credit allocations by seat type

Each seat type includes a credit allocation (see Seat management for details on seat types and how to assign them): Credits are tied to the individual user, not the seat. Changing or unassigning a seat does not revoke credits already allocated: the user retains them and can continue consuming them until the end of their current period. For details on how credits are drawn from different sources (individual allocation, workspace pool, overage), see Credit management.

Credit reset

Individual seat credits reset monthly, on the anniversary of your subscription start date. Unused credits do not carry over to the following month. Free seat credits are a one-time lifetime allocation and do not reset.