AiGAIN
Enterprise
—
Enterprise Plan
—
GAIN
behavioral signal
Token Usage — 30 Day Trend
Daily tokens consumed across all teams
Usage by Team
Share of monthly tokens
Mode Distribution
EXPLORE vs BUILD across teams
Intensity by Team
Average throttle level per team
Override Rate
Individual vs inherited policy
Org-Wide Behavioral Policy
Default state applied to all teams unless overridden
Recent Activity
Behavioral state changes across the org
Team Behavioral Policies
Members
Member Team Mode Intensity Depth Override
API Keys — One Per Team
Drop-in Anthropic Replacement
Replace https://api.anthropic.com with your AiGain endpoint. Pass your team key via x-aigain-key header. Behavioral state is injected automatically per team policy.
client = Anthropic(
  base_url="http://your-aigain-host/v1",
  api_key="ag-your-team-key",
)
Org-Wide Policy Rules
AiGAIN
What is AiGain?

AiGain is a behavioral control layer that sits between your organization and its AI usage. It controls how Claude thinks — not just what you ask it, but the cognitive mode it operates in when responding.

Every employee using AI today gets the same default behavior regardless of their role, their task, or what the company actually needs. AiGain fixes that.

The Problem It Solves

A support agent needs an AI that explores empathetically and asks clarifying questions. An engineer needs one that executes immediately and ships code. A researcher needs one that goes deep and surfaces trade-offs.

Without AiGain, all three get the same model behavior. Tokens burn. Quality suffers. The company has no visibility and no control.

How It Works

AiGain acts as a drop-in proxy for the Anthropic API. Your existing Claude integration points to AiGain instead of Anthropic directly. One line of code changes.

# Before
base_url = "https://api.anthropic.com"

# After
base_url = "https://aigain-production.up.railway.app/v1"

Every API call passes through AiGain. It looks up the team key, resolves the behavioral policy for that team, injects the right system prompt instructions, then forwards the request to Anthropic. The response comes back unchanged.

Behavioral Modes
BUILDExecute mode
Claude picks the best approach and implements it immediately. No alternatives presented. No thinking out loud. Output only. Ideal for engineering teams shipping code.
EXPLOREAnalysis mode
Claude covers multiple approaches, surfaces trade-offs, asks clarifying questions, and ends with decision points. Ideal for support, research, and strategy work.
The Control Hierarchy

Behavioral policy flows top-down, with each level able to override the one above:

Org Policy
Company-wide defaults. Every team starts here unless overridden. Set the floor and ceiling — min/max intensity, allowed modes, governance rules.
Team Policy
Each team gets its own behavioral preset. Engineering gets BUILD. Support gets EXPLORE. Research gets deep depth and high verbosity. One API key per team.
Individual Override
Senior engineers can unlock higher intensity. Specific roles can get tighter scope. Tracked and visible to admins.
What Gets Tracked

Token usage per team — see exactly where your AI budget is going.
Behavioral states — every policy change is logged with timestamp.
Active overrides — see which individuals are running outside team defaults.
Estimated savings — tokens saved by throttling teams that don't need max intensity.