Usage and billing
Two things can appear on your bill: seats, and usage.
The workspace is what is billed, and its subscription covers the people in it. Add a member and the seat count goes up; remove one and it goes down. The workspace owner is notified when someone joins, because that is the moment the bill changes.
A new workspace starts on a trial with no card required. A personal workspace cannot take members — convert it to a company workspace first.
Everything the product does on your behalf is metered in stable units: model tokens, workflow runs, browser time, speech, third-party calls. The full list is in the billing units reference.
Those unit names never change. That matters if you report on your own usage: build on the unit name and your reporting keeps working.
Whether usage is charged, and at what rate, depends on the plan your workspace is on. Some plans include allowances; some sell prepaid blocks. Your workspace’s plan page shows what applies to you.
Month-to-date figures are a preview. They are recalculated nightly, so a figure can move until the month closes. Once a month is closed it is fixed and does not change afterwards.
If prepaid credit runs out
Section titled “If prepaid credit runs out”Where your plan uses prepaid blocks and the balance reaches zero, new work declines rather than running and billing anyway. You will see this as a refusal on new workflow runs and chat turns. Top up and it resumes.
If the subscription lapses
Section titled “If the subscription lapses”An unpaid workspace becomes read-only. Specifically:
- Everything already there stays there. Nothing is deleted.
- You can still read it and export it.
- You cannot create new work — new runs, new records, new edits are declined.
- Billing, membership and profile changes keep working, because those are how you get out of it.
- Scheduled jobs, webhook triggers and embedded widgets stop rather than degrading. An embedded widget on your website declines politely instead of showing your visitors a billing message.
- These docs keep working. They are where you look up how to fix it.
A failed card does not stop you immediately: the payment provider’s retry window applies first, and only a definitive failure closes the gate.
Reading your usage
Section titled “Reading your usage”Your workspace’s usage view breaks spend down by unit and by what caused it — which workflow, which chat, which embed. That last one is why embedded widgets are tagged: if one embed on one page is responsible for a spike, you can see which.
If a figure looks wrong
Section titled “If a figure looks wrong”- A number changed since yesterday. Expected before the month closes; drafts recalculate nightly.
- One reply produced several speech charges. Expected: spoken replies are metered per sentence as they stream, and the parts sum to the whole.
- Usage you did not expect from an embed. An embedded widget bills the workspace that owns it, not the visitor. Check the embed tag in your usage view.