Skip to main content
On Business and Enterprise, every member has their own AI credits. Credits are pounds: Hive spends them on the AI work each member does, at what that work costs Hive, with no mark-up. One credit is 1p. Each seat includes credits every month for the person who holds it, and past them a member can keep working on extra usage if an Owner or Admin allows it. Every seat also includes 2,500 workflow runs a month. Every member sees their own credits, extra usage and runs in Settings → My usage. Owners and Admins turn extra usage on, set each member’s top-up limit and see what each member has left in Settings → Billing → Usage and spend limits, and see the workspace’s usage in Settings → Usage.
A workspace on Starter, Team or the earlier Business plan still has one shared credit pool, with top-ups and the rules that came with it. See Earlier plans.

Included credits

Each seat includes AI credits and workflow runs every month, for the member who holds it:
  • They are the member’s own. Nobody else can use them, and credits never move between members. A paid seat nobody holds includes no credits.
  • On Business, they are billed at cost. Each seat’s included AI credits are a line of their own on your invoice, such as Business Pro seat: Included AI credits, at 1p a credit, beside the seat’s platform part. Each member gets their seat’s full monthly credits whatever discount applies. See Invoice lines.
  • Credits Hive support adds, as a goodwill credit for example, go to one member’s own balance too, never to the workspace: Hive names the member they are for, who must hold a seat. They do not end with the month: they last until the expiry Hive gives them, if any.
  • They arrive each month once it is paid: when the month’s invoice is paid on monthly billing (on invoice terms, when the invoice is issued), and a month at a time through the year once the year’s invoice is paid on annual billing. A member who takes a seat part-way through the month gets the share of the month that is left. A new month’s credits wait for its payment: until a renewal’s payment goes through, or while a payment is overdue, no new month’s credits arrive. If the invoice that paid for them is refunded or lost in a payment dispute, its share of the credits is taken back. On an invoice that bills each seat as two lines, the money given back is set against the seats’ platform part, add-ons and extra usage first, so credits are taken back only for the share of the included AI credits lines it reaches. Once all of an invoice has come back to you, whether it was refunded, given back as account credit, or lost in a payment dispute (counting what was refunded or credited before the dispute), it adds no further credits: an annual one releases none of the year’s remaining months, and a member who takes a seat later in a month it paid for gets nothing from it, nor from an invoice for seats you added part-way through that month or year. See Refunds.
  • They do not carry over. Unused included credits end with the billing month, on the workspace’s billing date, and the next month starts afresh. During the trial they end with the trial instead.
  • A seat moved to someone else takes its credits with it. The new holder gets what the previous holder had left of this month’s credits, so the workspace never pays twice for the same seat.
  • A seat changed to one with more credits adds the difference for the rest of the month. A seat changed to one with fewer credits keeps this month’s, and gets the smaller allowance from the next month.
  • A member’s own included credits pay first, then extra usage, if the workspace allows it. See Extra usage.
  • During the trial, members hold Basic seats: £5 of AI credits and 2,500 workflow runs for each member, with no extra usage. See The free trial.
  • A workspace that changes from an earlier plan keeps what was left in its shared credit pool: it moves to the workspace Owner’s own credits, with the expiry it had. See Earlier plans.

What uses credits

The AI work Hive does on its own model accounts uses the credits of the member it is charged to (see Who pays):
  • Ask, in the app, in Slack and Teams, and through AI clients.
  • Hive AI in the deck editor: each request uses the credits of the member who made it, as an Ask answer does, and usage lists it as Decks, apart from Ask.
  • Agents and workflows: every AI step of a run, from any trigger, test runs included.
  • Building with Hive: the workflow assistant, the agent builder, the skill drafter and evaluation runs.
  • Signals: finding what needs attention in a member’s connected accounts, and preparing replies and actions.
  • The Business Brain, as it learns from a member’s sources in the background.
  • Deep research, images and web search.
  • Reading files: indexing the files a member connects or uploads, and reading scanned files and images.
  • Dictation: dictation uses your own AI credits, at what the transcription costs Hive.
These use no credits:
  • Approving, denying and undoing actions, and the audit log.
  • AI clients reading your data, and Hive reading your connected apps: neither uses an AI model. An AI client’s tool search (find_tools) does use one, and is charged as a knowledge search — see Hive MCP server.
  • Work on your own model key: your provider bills its tokens, and Hive adds no fee. See Bring your own key.
  • File storage and the search index.
  • The company overview and first-time setup research, which Hive pays for in full, with no limit on what they use.
Credits are worked out from the actual work done, so a long answer that reads several files costs more than a quick one. Small actions that each cost less than a tenth of a penny, such as searches, are measured on their summed cost: they add up, and a tenth of a penny is drawn each time their cost reaches one. Some languages use more tokens per character. Models count text in tokens, and text in Chinese, Japanese, Korean, Arabic, Hebrew, Hindi or Thai takes more tokens per character than English, so the same question asked in one of them can use more credits. Hive sizes what it reads by tokens, not characters, so a long file or web page in those languages is read in smaller parts of the same token size as English ones. See Limits reference.

What your credits buy

What common actions typically cost: £100 buys about 2,200 everyday answers on Hive Auto. An everyday answer is a typical answer on Hive Auto, and it is how Billing and plans shows what each seat’s credits do. What it costs Hive, in pounds. Model providers price their work in US dollars. Hive converts their prices at a fixed rate, so the same work always costs the same, and adds nothing on top. Price rises come with 30 days’ notice. Hive publishes a rise in what an action costs at least 30 days before it takes effect, and tells Owners and Admins in the Inbox (under Needs you), by email and, if they have linked Slack or Teams, as a direct message. A workspace on its trial, or one whose trial began after the rise was published, is not told: it signed up to the new prices. One rise is scheduled: from 1 January 2027, work on Gemini 3.8 Flash costs about twice as much, because Google’s introductory price ends. Your choice of model changes the cost. Hive groups models into three tiers: efficient, balanced and frontier. Hive Auto picks a model for each chat turn: short, routine questions go to the workspace’s Fast model and longer or harder ones to its Powerful model. Hive Auto’s Fast model must be an efficient model, or a custom or unpriced model that only your organisation’s own key runs; see Hive Auto’s Fast model. The figures above assume a balanced Powerful model. When you pick a model yourself, the model picker shows how much faster it uses credits than Hive Auto: about 2.7× for a balanced model and about 7× for a frontier model. Large actions ask first. Before an action estimated at more than £5 starts, such as a workflow run with many AI steps or an agent run on a raised budget, Hive shows the estimate in pounds and asks you to confirm, and the action is then held to the estimate you confirmed. Estimates are worked out at the same fixed rate your credits are spent at, so they match what the work costs. No single Ask answer or research run reaches £5: even exhaustive research on a Frontier model is about £3.40. A large company overview asks too, but Hive pays for it, so it is not held to the estimate. A workflow run or form submission that could take more than 50 agent steps asks too. See Runs past 50 agent steps.

Who pays

Every charge belongs to one member’s credits. Work a member starts uses their own; work nobody started uses the credits of the member it belongs to: What this means in practice:
  • A schedule’s owner pays for the automation they own. Give whoever runs your workspace’s automation a higher top-up limit, or Unlimited. A firm that runs a lot of automation may want one member, on a Max seat with an unlimited top-up limit, to own it.
  • A member whose accounts are busy carries the cost of Signals and Business Brain work on them, against their own credits and top-up limit.
  • When the member who pays has nothing left, background work on their accounts waits: items stay unprepared and Hive picks them up again on a later pass. Scheduled and app-event runs wait too: see When credits run out.
  • Background work always belongs to a member. Hive charges the AI work on an account to the member who connected it. AI work that Hive cannot match to a member, such as work on an app connected for the whole workspace before connections had owners, does not run: reconnect the app from the account of the member who should pay for its work.

Extra usage

When an Owner or Admin turns on Enable extra usage, members can keep using AI features after their included credits are used, up to their own top-up limit:
  • It is billed at cost, afterwards: 1p a credit, to the workspace’s card at the end of the billing period, on the subscription’s invoice. It is never discounted, and no member ever pays personally.
  • A top-up limit is extra, on top of the seat’s credits. It is not a total: a Pro member with a £50 limit can spend up to £80 in a month.
  • The workspace’s monthly maximum caps everyone’s extra usage together. It starts at £1,000 a month when you first turn extra usage on, and you can change it. Once the workspace reaches it, extra usage stops for everyone until the next month, even for a member with an unlimited top-up limit.
  • Off by default. With extra usage off, AI work stops when a member’s included credits are used.
  • Not during the trial. A trial has no card, so extra usage can be turned on once you choose a plan.
  • Not on a complimentary plan. It has no subscription to bill extra usage to: when a member’s credits are used, Hive support can add more.
  • Not while a payment is overdue. Members can still use their included credits, but extra usage waits until the invoice is paid.
  • Late usage: extra usage that reaches Hive after the invoice it belongs on was made, such as usage in the last minutes before a subscription ends, is billed on a separate invoice at the same 1p a credit, due in 30 days.
On Enterprise, the contract sets the workspace’s monthly maximum.

Usage and spend limits

Owners and Admins set these in Settings → Billing → Usage and spend limits, under Usage controls:
  • Turning extra usage on asks first. Switching on Enable extra usage opens Turn on extra usage?: members can keep working after they use their included credits, and extra usage is billed at cost on your next invoice. It lists the limits extra usage starts with, the Default top-up limit for each member and the Monthly maximum on extra usage for the workspace. Choose Turn on extra usage to confirm, or Cancel. Turning extra usage off happens at once, with no confirmation.
  • While extra usage is off, the note that AI work stops at each member’s included credits is followed by the maximum, for example “Monthly maximum on extra usage for the workspace: £1,000. You can change it once extra usage is on.” It is the maximum the workspace kept from when extra usage was last on, or £1,000 if it never set one.
  • While extra usage is on, one line above Top-up limits works through a Pro member’s month with your settings, for example “A Pro member (£30 included) with a £50 top-up limit can spend up to £80 this month. Extra usage is billed at cost on your next invoice, never more than £1,000 in total.” It is not shown on Enterprise.
  • During the trial, and once it has ended until a plan is chosen, a short card takes the place of the usage controls and Top-up limits: “After you choose Business, each member gets their seat’s AI credits every month (Basic £5, Pro £30, Max £60), reset on your billing date. You can let members keep working past them, billed at cost, within limits you set.” Its Choose a plan opens the plan picker.
Below them, Top-up limits lists every member who holds a seat, with their seat, the included credits they have left, their extra usage this month, their Top-up limit and the most they can spend. Choose a member’s limit there: £50 a month, £100 a month, £250 a month or Unlimited, or Default with the workspace default’s amount, for example Default (£50). A request waiting for a decision shows beside the member, with Review in your Inbox. A workflow has no monthly limit unless its owner sets a Monthly credit limit in its settings, and an agent has none: what each uses is bounded by the credits and top-up limit of the member who pays for it. Exhaustive research has no daily limit either. A few protections apply without any setting: AI clients can start at most £5 of work per member a day, and one answer can create at most 4 images. The member caps, Signals cap, public budget, workspace monthly limit, credit top-ups and auto top-up of earlier plans do not apply on Business.

Usage requests

When Allow usage requests and Enable extra usage are both on, a member who reaches their limit can ask for a higher one instead of waiting. A member reaches their limit when they have used their included credits for the month and all of their top-up limit.
1

The member asks

In Settings → My usage, or in the notice Ask shows when they reach their limit, they choose Request a higher limit, pick one of the limits above their own, add a note for the Owners and Admins if they like, and choose Send request.
2

Owners and Admins are told

Each Owner and Admin who holds a seat gets a card under Needs you in the Inbox, and an email. If none of them holds a seat, every Owner and Admin gets it, under Billing notices in Settings → Billing. Nobody is asked to decide their own request.
3

One of them decides

On the card, they choose the limit to approve (the one asked for, or another, Unlimited included) and Approve, or Decline. The member is told either way, and the other cards close.
  • Only at the limit. Request a higher limit shows only once a member has reached their limit. A member with credits or extra usage left cannot ask yet, and nor can one stopped by the workspace’s monthly maximum on extra usage: a higher limit of their own would not help, so an Owner or Admin raises the maximum instead.
  • Extra usage must be on. A top-up limit only applies while extra usage is on, so with it off nobody can ask: an Owner or Admin turns on Enable extra usage first.
  • Owners and Admins raise their own limit. At their limit, an Owner or Admin sees Raise your limit in Billing instead of Request a higher limit, and sets their own under Top-up limits in Settings → Billing → Usage and spend limits. Hive never asks anyone to approve their own request: one from an Owner or Admin whom nobody else could decide is refused with “Nobody else can approve this, so raise your own top-up limit in Settings → Billing → Usage and spend limits instead.” An Owner or Admin who opens a request of their own sees “This is your own request. You set your own top-up limit, so nobody needs to approve it.” and Raise your limit in Billing, with no Approve or Decline.
  • An approved limit stays until an Owner or Admin changes it.
  • One request at a time. While a member’s request waits, My usage says so instead of offering another.
  • A request lapses if nobody decides it by the end of the month.

When credits run out

When a member has used their included credits:
  • With extra usage off, their AI work stops until the next month’s credits arrive, an Owner or Admin turns on extra usage, or they are given a seat with more credits.
  • With extra usage on, they carry on until they reach their top-up limit or the workspace reaches its monthly maximum.
  • During the trial, their AI work stops until an Owner or Admin chooses a plan in Settings → Billing: a trial has no card, so it has no extra usage.
  • On a complimentary plan, their AI work stops until the next month’s credits arrive, or Hive support adds more: a complimentary plan has nothing to bill, so it has no extra usage and no top-ups.
  • Background work on their accounts waits: Signals and the Business Brain pick it up again on a later pass, once there are credits to pay for it.
  • Pictures and scanned files stay unread: a file synced from their accounts keeps the text Hive could read without AI and is marked for review with “Not read yet — out of AI credits; Hive reads it once credits are available”. Hive does not try again on every sync while there are no credits; the first sync after credits return reads it.
  • Scheduled and connected-app-event runs wait for up to 72 hours when their owner has nothing left, and start by themselves when credits return. A workflow with no AI step uses no credits and never waits, and a schedule keeps one run waiting at a time. After 72 hours a run stops waiting: Owners and Admins get a Run when credits return? notice under Needs you. In Settings → Billing → Runs waiting for credits, choose Run when credits return and the run starts as soon as credits are back. The run’s owner can choose it too.
There are no free quick answers on Business: quick answers belong to earlier plans. Ask shows why an answer cannot run:

Deck AI

Hive AI in the deck editor uses the member’s own AI credits, exactly as Ask does: each request is charged for the AI work it does, to the member who asked.
  • Reverting does not refund. A request is charged for the work it did, even if you then revert the changes it made to the deck.
  • A request refused before it starts costs nothing. When the member has no credits left, has reached their top-up limit, or the workspace is read-only or has a failed payment, Hive says why before it starts (see When credits run out for what fixes each). Nothing is charged and the deck is not changed.
  • Each request has limits. One request makes at most 150 steps (each read, check or change of the deck is one), enough to build and check a whole deck, and runs for at most 15 minutes. When it reaches its steps with work left, Hive AI says what it finished and what is left, and the task offers Continue: one click carries on where it stopped, as a new request in the same task, without redoing finished slides. A request that reaches 15 minutes stops and says so. Hive also stops a request that is repeating itself, doing the same thing again with nothing new done in between, or failing at every attempt, and says it stopped because it was repeating itself. In every case the changes it already made stay in the deck: to undo them, revert them from the request’s task, or restore the Before Hive AI auto-save in the deck’s File history. The work it did is charged as usual, and each request, Continue included, is checked against your credits before it starts and as it works.

Failed runs

When an agent run, a workflow run or a public agent exchange fails because of a fault on Hive’s side, Hive gives back what its AI work used, automatically, to the member who paid for it: the credits arrive in that member’s own balance and last 12 months.
  • Only what the run used of the member’s credits and extra usage comes back. Trial credits and work on your own model key were never charged, so they are not refunded.
  • Each run is refunded once, and Hive retries a refund it could not make straight away. If Hive has to run a workflow step again on its own, for example after a restart, what the first try used comes back in full.
  • Refunds in a month add up to at most 5% of what the workspace used that month.
  • A run that ran out of time because of its own size, one you stopped, one a limit stopped, and one the model rejected or refused for its input are charged as usual. Workflow test runs are not refunded. The same rules, in full, are in Earlier plans.

Workflow runs

Every seat includes 2,500 workflow runs a month, for the member who holds it. A workspace that needs more adds the execution add-on: 25,000, 75,000 or 200,000 runs a month for the whole workspace, on top of the seats’.
  • What counts. Every live run of a workflow, however it starts: Run live now, a form, a public form, a schedule or a connected app event. Test runs do not count, and a run that resumes after a wait, or that Hive recovers after a restart, is not a new run. A run that fails to start gives its run back.
  • Whose runs. A run counts against the member it is charged to, by the same rules as credits: yours for runs you start, the workflow owner’s for scheduled, app-event and public form runs. See Who pays.
  • Own runs first. A run uses its member’s 2,500 first, then the workspace’s add-on. No member has a cap on the add-on.
  • No carry-over. Runs reset each month, the member’s and the add-on’s alike.
  • When both are used, a run you start is refused: “This workspace has used its workflow runs for this month. An admin can add an execution add-on in Billing.” A scheduled, app-event or public form run is not started: it appears in the workflow’s Past runs as a Failed run that names the reason, Owners and Admins are told, and a public form tells the person submitting it that it was not sent. See Refused unattended runs still leave a record.
  • See them in Settings → My usage, for example Your runs: 1,840 of 2,500 · Workspace add-on: 3,200 of 25,000. Owners and Admins see the whole workspace’s under Plan limits in Settings → Usage: every member’s runs together, against what the seats they hold include, and the add-on’s, for example 4,960 of 10,000 members’ runs · 3,200 of 25,000 add-on runs. A seat nobody holds includes no runs. The meter turns amber at 80% of all of them, with an amber dot beside the figure, and red once they are all used, and Add an execution add-on (or Choose a larger execution add-on) appears beside it then.
A run uses AI credits as well as a run when its steps call a model; a run with no AI step uses only a run.

See your usage

Usage, invoices and credit history start on 12 October 2026, when Hive began taking payments: nothing from before then is shown here, in the CSV download or in Settings → Billing. Credits you can still use are listed whatever date they were added.
  • Settings → My usage, for every member: what their seat includes this month and what is left, their extra usage against their top-up limit (or that extra usage is off), when their credits reset, Request a higher limit once they reach their limit (Raise your limit in Billing for an Owner or Admin), and their workflow runs. During the trial it shows what the seat includes for the trial, that AI work stops once those credits are used until an Owner or Admin chooses a plan (an Owner or Admin reading it gets a Choose a plan link that opens the plan picker), and the date the trial, and its credits, end. Below that, what they spent this period by category and by where the work ran, in pounds and pence, with the tokens behind it. Where the work ran names the feature, such as Ask, Decks, Agents or Workflows.
  • Settings → Billing → Usage and spend limits, for Owners and Admins: the usage controls, and each member’s credits, extra usage and top-up limit, as described above.
  • Settings → Usage, for Owners and Admins:
    • Plan limits: your Basic, Pro and Max seats against the most your plan allows (300 on Business), and the workspace’s workflow runs this month. Business has no other plan limit, so nothing else is listed.
    • Spent by month: what the workspace spent on AI work in each of the last 12 months, in pounds. Choose a month to see its breakdown.
    • Breakdown: what was spent by member, product area, model, where the work ran or day, in pounds and pence. Spent is what the work cost; Paid from credits is what was paid from members’ own credits and, past them, their extra usage. You can download it as a CSV file. Select Show tokens to see the tokens behind each row. In the CSV’s funding column, work paid from a member’s own credits, and past them their extra usage, shows as own_credits: there is no shared pool.

Usage alerts

Owners and Admins are alerted as the workspace’s extra usage reaches 50%, 80% and 100% of its monthly maximum, and as a workflow with Usage alerts on in its settings reaches 50%, 80% and 100% of the Monthly credit limit its owner set (its owner is told too). Alerts arrive in the Inbox, by email and, if they have linked Slack or Teams, as a direct message. Each can mute Usage alerts for themselves in Settings → Notifications.

On earlier plans

Starter, Team and the earlier Business plan share one credit pool among the workspace’s members, with credit top-ups and auto top-up, Signals fair use, quick answers, member caps, plan limits and refunds for failed runs paid into the pool. A workspace on one of them keeps those rules until it changes plan: they are all on Earlier plans.

Billing and plans

Seats, prices and the execution add-on.

Trial and payments

The trial, checkout, invoices and failed payments.

Models

Choosing a model, and what each choice costs.

Earlier plans

The shared credit pool on Starter, Team and the earlier Business plan.