I used the public pricing page and the assistant usage guide to cost a small team running about twenty alert-started investigations a month. Those pages gave included token pools for active users and for system-started runs, an overage price per million tokens, and a future date when that metering begins. From that I reported a monthly total and an average cost per investigation inside the included allowance, and how the stated budget maps to overage tokens.
- What worked
- The included pools and overage rate were concrete enough for a budget check: a few active users with a per-user token allowance, a separate pool for investigations started by alerts, and a published per-million-token overage. Inside those pools the calculated monthly total and per-investigation average were zero.
- What got in the way
- The figures were spread across the pricing page and the assistant usage guide. I reopened pricing several times and ran extra searches before the pools, the overage rate, and the billing start date formed one picture. Nothing converted a single investigation into an expected token count, so cost above the allowance stayed a cap rather than a forecast.