Skip to content
Console

Billing and Plans

Billing shows what your plan allows right now.

Start here when a button is locked, disabled, or says upgrade required. Many blocked actions are plan or usage questions, not broken setup questions.

Billing is the source of truth for exact allowances: owned hubs, private skill setups, runtime operations, hub release operations, client connections, hub addresses, paid Skill Store access, and help options.

Some readers call this a billing wall, can’t add problem, plan gate, or upgrade required state. Check Billing before changing setup.

If you are just starting, Free Tier explains the smallest path: public hubs, one connection, narrow permissions, and Billing when a button is locked.

  • a button is locked or disabled;
  • a message says upgrade required;
  • you cannot create a hub or cannot add another connection;
  • runtime updates, hub updates, or private skill actions are unavailable;
  • hub addresses, paid Skill Store entries, or Live Map access are unavailable;
  • you need to separate a plan limit from a setup problem.
Billing page showing current plan, hub addresses, help options, limits, and plan messages.
Billing shows plan limits, hub addresses, skill access, and help options before a limit blocks you.

Limits

How many hubs, skills, clients, permissions, and daily uses your plan allows.

Runtime

Whether private skill setups, runtime config, skill updates, and runtime updates are available.

Hub updates

Whether owned hub capacity is available for hub creation and hub release operations.

Hub addresses

Whether custom hub addresses are available.

Skill Store

Whether paid Skill Store access is available for the workspace.

Help options

The help choices available for your plan.

Private skill setups means your plan includes space for your own skill groups and shared runtime settings. In plain language, it is what lets your workspace run hubs with their own skills instead of only using public hubs.

Plan itemWhy it matters
Owned hubsNeeded to create and run private workspace hubs.
Runtime slotsNeeded when private hubs need their own skills and runtime config.
Private skillsNeeded when your own hubs need custom skill groups.
Client limitControls how many client connections can be created.
PoliciesControls how many access policies can govern clients and hubs.
Daily intentsControls daily live hub intent previews and usage.
Hub addressesAllows custom hub addresses for the workspace.
Public hub listingAllows hubs to appear in discovery.
Paid Skill Store accessShows whether the workspace can use paid entries if they are offered.
Live MapMay depend on owned hubs or private workspace features.
PathGood forUsually includes
Free pathLearning, trying public hubs, and creating a simple connection.Public hub discovery and an included connection allowance.
Workspace pathRunning owned hubs and private skill setups.Owned hubs, private skill setups, runtime and hub update access, hub addresses, more connections, and help options.

If you land on Billing from a locked button or page, Billing explains why. For example:

  • owned hubs require room for owned hubs;
  • private skill groups require the right plan;
  • runtime config requires private skill setups;
  • runtime updates require runtime capacity;
  • hub updates require owned hub capacity;
  • more connections require room for more client identities;
  • paid Skill Store entries require a plan that explicitly includes them;
  • Live Map may require a plan that includes owned hubs.

When a page sends you to Billing, read the gate in this order:

  1. Action: what is unavailable right now.
  2. Current limit: whether the workspace has reached a limit.
  3. Plan path: whether the action needs a different plan.
  4. Status: whether the status page shows a wider incident.
  5. Help options: where to ask if the limit does not match what you expect.

This keeps plan questions separate from setup questions. If the plan allows the action but it still does not work, return to the page you came from and read the status message.

Use the locked button scenario when you need to decide whether a blocked action is a plan limit or a setup issue.

Use Free Tier when you want the no-surprises route before choosing a paid workspace plan.

Billing is clear when you know:

  • which plan you are on;
  • which limit or feature affects your next action;
  • whether current usage has reached that limit;
  • whether help options are available for the question;
  • which page to return to after the plan check.