Skip to main content

​
The gates

Real-time human chat on escalate is available on every plan and is deliberately not gated.
remove_branding is the one entitlement a plan upgrade cannot grant. It comes only from the purchased add-on, so it resolves from a workspace flag rather than from the tier — which is why the highest plan alone does not remove the badge.

​
The one that catches people out

The MCP server and agent artifacts need Growth, because they use the same agent_write gate as write execution.On Starter, or during a trial, /api/mcp/{workspaceId} returns “Agent channel not available for this workspace” and /api/agent/{pk}/{artifact} returns 404. Nothing about the URL is wrong; the plan is.

​
Effective plan

Your workspace’s plan string is resolved to an entitlement tier before any check: Resolution fails closed. An unknown plan string never grants a feature by accident.

​
Active entitlement

A tier check is not the whole story. A workspace must also be entitled to serve at all, and three things independently revoke that:
  • the kill switch is on;
  • the trial has expired;
  • the subscription has lapsed.
Any of them and no gated feature resolves, whatever the plan says. The add-on entitlements are checked the same way — a purchased add-on on a workspace that is not entitled to serve grants nothing.

​
What a non-entitled workspace does

The behaviour is chosen per surface, so a lapse degrades rather than breaks.

The widget does not mount

The widget is told on load, before the cursor shows — no cursor, no crawl, no agent calls.

The agent goes quiet

The agent returns an empty, completed plan rather than an error, so a widget already on the page stops acting instead of throwing into it.

MCP stops answering

Both endpoints return “Agent channel not available for this workspace.”

Artifacts stop serving

404 with “Agent access is not enabled for this workspace.”
Lead capture and meeting booking stop entirely rather than degrading, since there is no partial version of either. The gate is enforced on the server, so an unentitled workspace does not capture leads or offer bookings through any channel.

​
Credits, separately

Distinct from plan gating, a workspace consumes credits. When the pool is exhausted:
  • the widget does not start a new session;
  • a new conversation is refused before any model spend, while conversations already in progress continue;
  • narration stops and the widget runs text-only.
The widget is given its remaining narration budget on load and decrements it locally, so a session that runs out of voice mid-conversation goes quiet without a round trip per utterance.

​
Rate limits scale with the plan too

See Rate limits — Starter, Growth and Scale each get their own ceilings.