Admins choose which ones people may use in Policies (License model). For each call, the gateway decides in this order:
1. A person’s own Claude plan
Using a person’s own Claude plan is available to organizations where xpander has enabled it. Contact xpander to turn it on.
- the person uses Claude Code, signed in with their Claude plan, and sends their xpander key in the
x-xpander-api-keyheader - the model is a Claude model from Anthropic
- Bring your own subscription is on for the person’s organization, group and agent
When the plan hits its limit
When someone’s plan hits its limit in Policies decides what happens until the plan resets:
When your organization falls back, each person can still choose to pause their own calls: When my Claude plan hits its limit in AI models & keys offers Continue on company models or Pause. When your organization pauses, that choice is locked for everyone with Your admin set calls to pause when a plan hits its limit.
While a plan is limited, AI models & keys says so, for example Your Claude plan’s usage limit is reached until Thu, Oct 8, 8:00 AM. Calls use company models until then.
2. Company models
Every other call, and a call a limited plan falls back from, runs on company models: a key your organization stored, or xpander’s key. Default license model in Policies decides which.
With Bring your own key, the stored key used is the first one assigned in this order: the agent making the call, the person, the person’s primary group, then the organization default for that provider (Whose key pays).
Cloud, Hybrid and Air-Gapped
On a Hybrid or Air-Gapped install, add a key for every provider your people use. A call for a provider with no key is refused. When some of your agents run on your install and others in xpander cloud, the agents in xpander cloud may still use Included with xpander.

