> ## Documentation Index > Fetch the complete documentation index at: https://docs.xpander.ai/llms.txt > Use this file to discover all available pages before exploring further. # Licenses and who pays > Included with xpander, bring your own key, or a person's own Claude plan: the order the LLM Gateway follows on every call, what happens when a plan hits its limit, and how it differs on Hybrid and Air-Gapped installs. Every call through the LLM Gateway is paid one of three ways, called license models: | License model | Who pays | Credits | Budgets | | - | - | - | - | | **Included with xpander** | xpander, on its own provider keys | Billed in credits | Counts | | **Bring your own key** | Your organization, on a provider key you stored | None; your provider bills you | Counts, at the cost the gateway measures | | **Bring your own subscription** | The person, on their own Claude plan | None | Counts toward none | Admins choose which ones people may use in [Policies](https://platform.xpander.ai/governance/policies) ([License model](/run/llm-gateway/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. A call runs on the person's own Claude plan, including any extra usage the plan has, when all of these hold: * the person uses Claude Code, signed in with their Claude plan, and sends their xpander key in the `x-xpander-api-key` header * the model is a Claude model from Anthropic * **Bring your own subscription** is on for the person's organization, group and agent If any condition is not met, the call is refused with a message that names what is missing. The call is never silently moved to company models. ### When the plan hits its limit **When someone's plan hits its limit** in [Policies](https://platform.xpander.ai/governance/policies) decides what happens until the plan resets: | Setting | What happens | | - | - | | **Fall back to company models** (default) | The call continues on company models, as in step 2, and the person sees that their plan is limited and when it resets. | | **Pause** | The call is refused until the plan resets, with the reset time. Nothing is charged to your organization, and people can't choose to continue. | 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](https://chat.xpander.ai/?settings=my-gateway) 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](https://platform.xpander.ai/governance/policies) decides which. | Default license model | A key is stored for the provider | No key is stored | | - | - | - | | **Bring your own key** | Your key. The provider bills you; no credits are used. | xpander's key, billed in credits, when **Included with xpander** is on. Otherwise the call is refused and names the provider that needs a key. | | **Included with xpander** | xpander's key, billed in credits. Your stored key is not used. | xpander's key, billed in credits. | 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](/run/llm-gateway/providers-and-keys#whose-key-pays)). ## Cloud, Hybrid and Air-Gapped | Your organization runs on | Keys a call can use | | - | - | | xpander cloud | A person's own Claude plan, your stored keys, and xpander's keys when **Included with xpander** is on | | Hybrid | Agents on your install: your stored keys and the credentials your install provides. Your people's coding tools, which connect through xpander cloud: their own Claude plan and the keys you stored in xpander. xpander's keys are never used for either. | | Air-Gapped | Your stored keys and the credentials your install provides | 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**. ## See who paid Open a request in [Logs](https://platform.xpander.ai/governance/logs). **License model** shows how it was paid, its **Gateway decisions** show whether the plan, a stored key or xpander's key served it and why, and the **License model** filter lists the requests paid each way. In [Usage](https://platform.xpander.ai/governance/usage), the tiles split spend into **Subscription: xpander credits**, **Subscription: your provider keys** and **Subscription: personal Claude and ChatGPT plans**. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.