Category Allocation

How monthly AI spend is split across Hannibal, Marcus, Constantine, Cato, and H1 Triage, and what a 0% slice does to automation.

Category Allocation on Settings → AI splits the account's monthly AI spend across use cases. It does not change the monthly amount.

Categories

Use case

What it covers

Autonomous Penetration Testing

Hannibal hunts, manual and scheduled

AI Assistant

Marcus sessions

Source Code Analysis

Constantine scans

Vulnerability Validation

Cato, including Automatic Findings Validation

Bug Bounty Validation

Bug bounty report triage

Domain/CIDR Range Ownership Validation

Pius

If the account has no AI budget yet, the card shows Not provisioned yet. and cannot be edited.

Edit the allocation

  1. Click Edit on the card.
  2. Turn on Allocate budget by category. The switch needs a monthly budget above $0. The first time you turn it on, Guard applies the Balanced preset.
  3. Pick a preset (Balanced, Pentest focused, or Equal) or set each Allocation share yourself. The table also shows Used this month and the resulting Monthly limit for each use case.
  4. Save when the total reads 100% allocated. Shares are whole percentages.

Guard shows Category allocation updated when the save succeeds.

Turning Allocate budget by category off and saving removes every category limit. That is different from setting a category to 0%.

What 0% does

If you set Autonomous Penetration Testing or Vulnerability Validation to 0% while its automation is on, the editor warns, for example Saving will pause Automatic Penetration Tests. Saving is still allowed. The automation's switch stays on, and its card shows Paused — category budget is $0 until the category has budget again.

Who can edit

Users with permission to manage settings. Changing the monthly amount itself requires a super-admin; see Monthly AI Spend.