Billing and limits

Your plan, what you have used, and where the ceilings are.

Settings → Billing

Rows marked not measured have a cap but no usage reading behind them.

Plan and credits

The plan card shows what you are on and what it costs: Free, at $0 per month, until you upgrade. See plans is the upgrade control, and the only one on the page.

Credits this period tracks AI usage against the allowance. It is the same number as the AI credits readout in the top bar, and the popover behind that readout is where the detail lives: tabs for Your usage and Org total, a By agent breakdown, and a reset at the start of the calendar month, UTC.

Limits

Each quota is listed with usage against it. Customize customer limits overrides limits for a single customer.

Limit	Scope
API keys	per customer
Events	per day, per minute
API calls	per day, per minute
Active integrations	total
Connectors allowed	total
Workflows	per customer
Steps	per flow

Workflow categories and Workflow labels are listed here too, both scoped per workspace and counted live, so the usage reading against them is real. They are the two registries behind Workflows Tags, and that page is where you add and remove them.

The list continues past the visible area with further rows: concurrency, AI sessions and tokens, retention, storage, connected accounts, users, webhook endpoints, payload size, executions and AI credits are all reported to appear further down. Scroll the page and read the rows themselves rather than relying on that list being complete or the scopes being as described.

Going over a limit stops new work rather than charging you, and nothing already running is interrupted. No surprise invoices, but also no silent overage: a sync that stops because you hit a ceiling looks like a broken sync until you check this page.

Below the fold

Sections further down this page (Customer tiers and Create tier, Usage by customer, Payment and Invoices), have not been captured, so this page does not describe how they behave. Read them in the product before planning around them.

One thing about tiers is corroborated from elsewhere: the Roles screen states that a custom role can be assigned to an embed tier under Billing, which is how you scope what an embedded end user may do.