Connect Hatz AI
Hatz AI is the AI workspace MSPs deliver to their customers. Connect your Hatz MSP account to Waxell and you get one inventory of the agents, apps and workflows across every customer tenant you manage — who uses them, how often, and with which models.
One key covers your whole MSP. Waxell tags every agent with the customer it belongs to, so you can see each customer's AI footprint side by side.
What Waxell can see
Read-only, through the Hatz API:
- Agents — name, model, tools, knowledge sources, and whether tools are picked automatically.
- Apps and workflows — name, default model, and number of workflow steps.
- Usage per customer — for each agent over the last 30 days: number of runs, number of distinct users, models used, where it was used (chat, API, workflow), and the customer tenants using it.
- Activity — who ran which agent with which model, in which tenant, plus the compliance audit trail (sign-ins, API key changes, compliance exports).
Conversation capture is opt-in. By default Waxell stores usage metadata only — message bodies, attached files and agent system prompts are dropped. A workspace owner or admin can turn on Capture prompts & responses (see below) for full observability.
Before you start
You'll need:
- A Primary Admin login to the Hatz admin portal (admin.hatz.ai).
- For per-customer usage: the invocation log enabled for each customer tenant you want covered (step 3 below).
Connect
- Create a Hatz API key. Sign in to admin.hatz.ai as a Primary Admin, open Settings → API Keys, and generate a key. Name it Waxell so it's easy to recognise later.
- Add the connection in Waxell. Open Agent Discovery → Connections → Add connection and choose Hatz AI (under MSP platforms).
- Turn on the invocation log (recommended). In the Hatz admin portal, open Compliance & Audit Logs for each tenant and enable the invocation list. This is what lets Waxell attribute usage to each customer. Tenants without it still contribute their agents, apps and workflows — just without usage data.
- Paste the key and select Verify & connect.
- Leave Hatz tenant ID blank to cover every customer tenant your MSP manages.
- Enter a tenant ID to limit this connection to one customer — useful when each customer has its own Waxell workspace.
Waxell checks the key with Hatz before saving it. A key that's wrong, expired or revoked is rejected on the spot with Hatz's reason. A good key shows your MSP and how many tenants it manages — for example Key verified — Northwind IT · 42 tenants — and the connection moves to First sync scheduled.
The first sync
Because one Hatz key can cover dozens of customers, the first inventory is scheduled rather than run on the spot. It typically completes within one business day. When it does, the connection changes to Connected and your agents, apps, workflows and activity appear. After that, everything refreshes automatically every 10 minutes.
What you get
Open Hatz AI from the Connections tab to reach its platform page:
- Customer tenants — every customer, ranked by 30-day runs, with its share of total usage and number of agents.
- Model mix — which models your customers' agents actually use.
- Agents — every agent, app and workflow with its customer tenants, 30-day runs, users and models. Filter by posture band, search by name, and sort any column.
- Activity — invocations and audit events, each linked to the agent it belongs to.
- Agent pages — for any agent: its tools, knowledge sources, models, the customers using it, and when it was last used.
If some tenants don't have the invocation log enabled, the platform page tells you, along with how to turn it on.
Conversation capture (opt-in)
For full observability of what your customers' agents are asked and answer, turn on conversation capture:
- In Hatz, enable content access for the tenant under Compliance & Audit Logs (Primary Admin or Compliance Manager).
- In Waxell, open Hatz AI → Controls and switch on Capture prompts & responses. Only a workspace owner or admin can, and Waxell asks you to confirm.
Each Hatz chat session then appears on Executions as a governed run with its full conversation, the model used, the user and the customer tenant. Captured content follows your workspace's capture retention and redaction settings. File contents are never captured — only file names and types. Every change to this setting is recorded in your audit log with who made it.
Turn it off at any time; Waxell stops capturing immediately.
Spend
Hatz meters usage in credits. The Spend tab shows credits over the last 30 days by model, by agent or app, and by user, plus each customer tenant's credits used against its limit. To see dollars, enter your price per credit (from your Hatz plan) under Controls → Credit pricing — Waxell never estimates it.
Model prices through Hatz
The Spend tab also lists every model your Hatz tenants use, with the price per million tokens Waxell applies to it when it runs through Hatz. Each starts at the model's list price; a workspace owner or admin can change it to what Hatz actually charges. A Hatz price only affects Hatz — the same model used directly or through another provider keeps its own price.
With conversation capture on, each Hatz run on Executions carries a cost. Hatz doesn't report token counts for chats, so the cost is estimated from the captured conversation (about four characters per token) and labelled as an estimate. These costs also appear in Waxell's cost views under the provider Hatz.
After changing a price, select Recompute costs to re-price every Hatz run Waxell has already stored.
Scoping: one workspace or one per customer
| You want | Do this |
|---|---|
| One view of every customer (MSP-wide) | Connect in your MSP's own Waxell workspace and leave Hatz tenant ID blank. |
| Each customer in its own Waxell workspace | Connect in each customer's workspace with the same key and that customer's Hatz tenant ID. Waxell confirms the tenant is one your key manages. |
Changing the tenant on an existing connection starts a new first sync for the new scope.
Revoking access
Delete the Waxell key under Settings → API Keys in the Hatz admin portal, or disconnect Hatz AI from its Settings panel in Waxell. Either ends access immediately. Disconnecting in Waxell also removes the discovered inventory.