How we define a Credit
In short, a Credit is the unit Cora uses to measure the AI work it does for you. Your plan includes a monthly allowance of Credits, and each piece of AI work draws from it. Work that takes more AI effort uses more Credits. A quick check on an account uses a few; a detailed account brief or a chat answer that pulls together your full account history uses more. A few things to keep in mind:- Credits count the same way no matter how the work starts: from the Cora app, Slack, a scheduled agent, or a signal.
- Only AI work uses Credits. Rule-based calculations, internal system steps, and viewing what Cora already generated are free.
- Credits include work Cora does based on configurations you set up, or that Cora set up with your approval.
The four kinds of work that use Credits
Your usage is reported in these four groups. Typical Credits are averages; actual usage depends on how much your agents do and how much context each task needs.How Credits are counted
A Credit is used whenever Cora runs AI to do work for you. Work that involves no AI is not counted.- Monthly allowance. Your plan includes a set number of Credits each month. Allowances run on calendar months and reset on the 1st. Unused Credits do not carry over.
- Your first month. If your plan starts mid-month, you get the full allowance for that month.
- Going over. Credits used beyond your allowance are billed at your plan’s overage rate, shown on your order form, and invoiced monthly.
- Checking your usage. Ask Cora in chat how many Credits you’ve used this month, by kind of work, or how this month compares with earlier months. Your Cora team will reach out as you get close to your allowance. Asking uses Credits like any other chat message.
- Changing plans. If you consistently use more than your allowance, moving to a larger plan usually costs less than paying overage. Plan changes take effect on the 1st of the next month.
Examples
These lists are illustrative, not exhaustive, but they cover the most common cases.Uses Credits
- An agent checking an account for changes and deciding whether to act.
- An agent drafting or sending an email, posting to Slack, or updating a Salesforce or HubSpot record.
- An agent querying your CRM or data warehouse to complete a task.
- Asking Cora a question in the app or Slack.
- Generating or refreshing an account brief.
- Generating an artifact, such as a QBR deck or a scoping document.
- Cora suggesting a next best action for an account.
- An outbound call placed by an agent.
Does not use Credits
- Viewing data that is already in Cora, including re-opening or downloading something Cora already generated.
- Values calculated with fixed rules rather than AI, such as formula, banded, rule and rollup columns.
- Automatically syncing your data into Cora, such as calls, emails, CRM records or warehouse data on a schedule.
Good to know
- One agent run can use Credits across several steps. For example, an agent that checks an account, pulls its recent activity and drafts an email uses Credits for each step. Most checks end in one step when there is nothing to do.
- Chat answers include everything Cora does to reply. Lookups and steps Cora takes to answer a message are included in that message’s Credits, not counted again.
- Longer chats use more Credits per message, because Cora reads more of the conversation each time. Starting a new chat for a new topic keeps usage down.
- Using Cora from your own AI assistant through MCP, such as ChatGPT or Claude, does not use Credits, because your assistant does the AI work. If you start an agent run through MCP, that run uses Credits like any other agent run.
- Moving from Actions. If your plan was set up in Actions, your order form explains how your allowance converts to Credits. Your total contract value does not change.

