This guide is for MSP admins. It covers turning on AI Gateway USD billing in the admin console, choosing budgets, opting tenants in, and managing tenants afterwards. For what the AI Gateway bills and how pricing works, see AI Gateway: pay for API usage in USD in this collection.
Before you start
You need the Manage LLM Gateway permission. The built-in Primary Admin, Admin and Billing Manager roles include it.
Your MSP needs an active Hatz package. Some setup items can only be fixed by Hatz, such as a missing billing account or package price. The page lists each one with "Contact Hatz support".
Decide three monthly budgets, in USD: a combined cap for all tenants, a starting budget for each tenant, and the highest budget a tenant can set.
Activation is one-way. It can't be undone, and it doesn't switch back to Hatz credits on its own; Hatz support can only suspend it. Each tenant still has to opt in separately, and a tenant that opts in can't switch back to Hatz credits.
Activate the AI Gateway
In the admin console, open Settings → AI Gateway. The status reads Not configured or Not enabled.
Read What changes when you enable gateway billing. It explains USD billing, pricing, how long request data is kept, and what can't be undone.
Enter the three budgets:
Combined monthly cap, all tenants (USD): total gateway spend across every tenant. Requests stop for everyone when it's reached.
Starting budget per tenant (USD): the budget a tenant gets when it opts in.
Highest budget a tenant can set (USD): the most a tenant admin can raise their own budget to. It can't be lower than the starting budget.
A tenant's budget may be higher than the combined cap. The combined cap still limits total usage across every tenant.
Review Legacy credits (grandfathered). These tenants keep paying in Hatz credits until they opt in. See Tenants that keep legacy credits below.
Select I accept the billing and retention notice above and have reviewed the grandfathered tenants, then click Activate AI Gateway.
When it finishes, the status reads Active, with the date it was enabled. If activation stops partway, click Retry activation; it picks up where it left off. If the page says another administrator started activation, ask them to finish it. If the list of grandfathered tenants changes before you finish, review the new list and accept the notice again.
Tenants that keep legacy credits
A tenant keeps Hatz credit billing for the Anthropic Messages and OpenAI Responses endpoints if it made credit-billed requests to them with an API key before your MSP activated the AI Gateway. Requests made with a key that has since been deleted still count.
The list is fixed when you activate. Tenants aren't added to it later, so a tenant created after activation must opt in before it can use these endpoints.
A tenant leaves the list when it opts in. From then on it pays in USD.
Every other tenant's requests to these endpoints are refused until it opts in.
If a tenant you expected on the list is missing, opt it in or contact Hatz support.
Opt tenants in
Activation doesn't enroll any tenant. Each tenant opts in once, in one of two ways:
The tenant's admin opts in on the tenant's Connect a client page. This needs the Manage tenant LLM Gateway permission, which the built-in Client Admin role includes.
You opt a tenant in on its behalf. In Settings → AI Gateway, find the tenant in the tenants list and click Turn on, or Switch to USD billing for a tenant that keeps legacy credits. Select I accept this notice on behalf of the tenant and confirm. Your acceptance is recorded.
Opting in applies the starting budget, or the tenant's own default if you've set one. It can't be undone.
Disable or re-enable a tenant
In the tenants list, click Disable next to a tenant. This takes effect immediately, with no confirmation step:
The tenant's new gateway requests are refused, including tenants that keep legacy credits. Requests already running finish.
Its API keys, opt-in and budget are kept.
The tenant sees Disabled by your provider on its Connect a client page.
Click Enable to restore access.
Manage budgets
Change the three budgets under Budgets, then click Save budgets. Changing the combined cap needs an active package; if none is found, contact Hatz support.
Set limits for one tenant with Overrides in the tenants list: a Default override (USD) and a Maximum override (USD). Leave a field blank to use your budget settings.
Lowering a maximum also lowers any tenant budget above it. The page names the affected tenants before you save.
Tenant admins change their own budget on Connect a client, up to the maximum you allow.
How budgets behave:
Changes apply to the next request, and may pause requests for a moment while they take effect.
A budget set below this month's spend stops new requests until the next month. Requests already running finish.
Budgets reset at the start of each calendar month in UTC.
The spend shown on the page is settled spend toward your budgets, not a final charge. Requests that are still running also use up budget, so requests can stop before the figure shown reaches a budget.
When the combined cap is reached, new requests stop for every tenant, including tenants still under their own budget.
Warnings and emails
Tenant budgets add up to more than your combined cap. This warning shows on every admin console page when the budgets of opted-in tenants add up to more than the cap. That's allowed, but some tenants may be stopped before they reach their own budget. It clears once you raise the cap or lower tenant budgets.
At least 80% of your combined monthly cap is spent, and then Combined monthly cap reached. These show on every admin console page. You can dismiss one until the next threshold or the next month.
Email. Primary Admins and Admins get an email when spend reaches 80% and 100% of the combined cap, with a subject like "LLM Gateway: 80% of your monthly budget reached". Each is sent once per month. Changing the combined cap re-arms them; changing tenant budgets doesn't.
If the AI Gateway is suspended
Hatz support can suspend the AI Gateway for an MSP. The status then reads Suspended. While it's suspended, USD requests are refused and tenants that keep legacy credits continue on credits. Contact Hatz support to resolve it.
Related articles
AI Gateway: pay for API usage in USD, in the MSP / Admins collection
AI Gateway errors, in the FAQs / Troubleshooting collection