Access control
How to manage an organization's users, invitations, teams, roles and approval rules, and how built-in and custom roles grant permissions.
Audit log
How to review, filter, inspect and export the organization audit log, including restricted details, CSV exports, retention per plan and the audit API.
Access control
How to manage an organization's users, invitations, teams, roles and approval rules, and how built-in and custom roles grant permissions.
Audit log
How to review, filter, inspect and export the organization audit log, including restricted details, CSV exports, retention per plan and the audit API.
How an organization chooses a plan, pays through Stripe Checkout and the Stripe Customer Portal, and tracks metered usage, credits and limits on the Usage and Limits page.
Billing covers the organization's subscription to the platform. Usage covers what the organization consumes during the billing period and how that compares with its plan.
Both pages live under Organization, Account in the sidebar:
| Route | Purpose |
|---|---|
/{orgSlug}/billing | Billing: current plan, billing details, payment methods and invoice history. |
/{orgSlug}/billing/checkout/return | Landing page after Stripe Checkout. |
/{orgSlug}/billing/manage/return | Landing page after the Stripe Customer Portal. |
/{orgSlug}/usage | Usage and Limits: current-period usage per meter. |
This page is about paying for the platform. For invoices that the organization sends to its own customers, see Invoices.
| Plan key | Name | Summary |
|---|---|---|
starter | Starter | Free and limited, for evaluation. Every organization starts here. |
pro | Pro | Self-serve plan for small teams that need AI, inbox, API and workflow credits. |
business | Business | Higher included credits, unlimited active users and longer audit log retention. |
enterprise | Enterprise | Custom, quote-only plan with volume-based credit pricing, dedicated support and onboarding. |
Pro and Business are sold as credit packages, billed monthly or yearly. Larger packages include more credits, and unused credits roll over: the page shows the current package credits plus unexpired rollover credits, and the oldest balance is used first. Enterprise is arranged with the platform team and cannot be selected in the app.
Plans, packages, prices and limits are managed by platform administrators in Admin plans, so the exact numbers can differ per deployment.
Usage is recorded per meter in an append-only ledger and summed for the current billing period. Billable meters count toward the plan and can produce overage:
| Meter | Counts |
|---|---|
ai.input_tokens | Input tokens for AI chat, suggestions, agents, inbox auto-replies and workflows. |
ai.output_tokens | Output tokens for the same features. |
inbox.messages_received | Inbound messages on connected inbox channels. |
inbox.messages_sent | Outbound human and AI replies on connected inbox channels. |
api.requests | Organization-scoped REST API requests. |
mcp.tool_calls | External MCP tool calls. |
workflow.steps | Weighted workflow steps. |
files.storage_bytes | File storage, which also sets the Files storage quota. |
workflow.steps is the billable workflow meter. Actions and AI steps count once, paid registry lookups such as a KvK lookup carry a higher weight, and flow control such as triggers, conditions, delays, stages, waits and approvals is free. Steps that are skipped bill nothing. Lifecycle runs and test runs are not billed. workflow.runs is tracked for reporting only.
Other meters are tracked without billing: knowledge retrievals, memory operations, file uploads and extractions, media processing, email deliveries, notifications and active users. Active users are still a plan limit.
Each plan sets an included quantity and an enforcement mode per meter:
| Mode | Behavior |
|---|---|
| Hard limit | Features that check an allowance, such as AI turns and workflow steps, are blocked once the included quantity is used. Starter uses this mode. |
| Included plus overage | Usage above the included quantity is billed as metered overage. Pro and Business use this mode. |
| Soft limit | Usage is tracked against a custom or unlimited allowance. Enterprise uses this mode. |
AI chat checks the AI allowance before a turn starts, and starting a workflow action checks the step allowance first. Overage is reported to Stripe metered billing, while the local ledger stays the source of truth for the Usage and Limits page. An hourly workflow emails organization owners when usage crosses 80 percent and 100 percent of an included quantity.
Open Billing. The Current plan section shows the active plan, its features and credits, and Choose a plan. Pick a plan, a credit package and Monthly or Yearly, then continue to Stripe Checkout. After payment you land on the checkout return page.
The return page is only a hint. Stripe sends the final subscription update through a verified webhook, so the Billing page can show Stripe is finalizing your plan for a short time. Refresh if the change is not visible yet.
Select Manage in Stripe, or Manage payment methods in the Payment methods section, to open the Stripe Customer Portal. Cards and payment methods are managed in Stripe; the app stores only safe display metadata for them. After you leave the portal you land on the manage return page.
The Billing details section holds the company name, billing email, invoice email recipients, address and tax ID with its type, such as EU VAT or Dutch BTW. These details appear on subscription invoices.
Invoice history lists the subscription invoices from Stripe with their status. Select a row to download the Stripe invoice PDF.
Open Usage and Limits to see, for each meter, the current-period quantity against the included quantity, credits used and estimated overage. The page also shows the total credit limit, whether auto top-up is enabled and the latest usage events recorded in the period. Explain usage asks the assistant side panel to walk through the numbers.
| Key | Grants |
|---|---|
organization.billing.manage | Open Billing and Usage and Limits, start checkout, open the Stripe Customer Portal and edit billing details. |
Platform administrators manage plans and subscriptions with system.billing.view and system.billing.manage. See Admin billing and Access control.
The automatic Billing usage threshold workflows publish an event when usage crosses a threshold and email the organization owners. See Workflows.
Billing has no MCP tools and no organization REST resources. Checkout, the portal and billing details run as server actions in the app. Stripe calls POST /api/v1/billing/stripe/webhook to update the local billing state.
Last updated on
Access control
How to manage an organization's users, invitations, teams, roles and approval rules, and how built-in and custom roles grant permissions.
Audit log
How to review, filter, inspect and export the organization audit log, including restricted details, CSV exports, retention per plan and the audit API.
