They act in loops
One task can mean dozens of model calls, each a chance for data to leave.
AI agents
Agents don't wait for a person to press send. They plan, call tools and models in loops, pass data between each other and act on the results. agentKeyRoute gives every agent its own identity and policy, checks every step it takes, and records all of it.
Why agents need governance
One task can mean dozens of model calls, each a chance for data to leave.
A database row or a file an agent reads goes straight back into its next prompt.
In multi-agent systems, data moves between agents with different jobs and different rights.
An agent stuck in a loop can burn through a month's budget overnight.
Every agent governed
Register each agent as a workload and give it its own key. From then on, every call it makes is tied to that agent, its team and its governance profile, whichever framework it's built with.
A key per agent carries its team, its workload and its governance profile, so two agents in the same system can follow different rules.
Mark an agent as assistive, human-in-the-loop or autonomous. Autonomous agents score higher risk, and the EU AI Act framework holds autonomous high-risk agents for human oversight.
Every message an agent sends is scanned, including the tool results it passes back to the model, and redacted or blocked before it leaves.
Set a monthly budget on the agent's workload. When it's spent, the agent's requests stop with a clear error instead of a surprise bill.
Stop one agent, revoke one key, or stop every agent in the organisation at once, from the console.
Responses carry the decision, the rule that applied, the risk score and a request ID, so agents and their developers know exactly why something was redacted or blocked.
Multi-agent systems
An orchestrator hands work to specialist agents. With agentKeyRoute in the middle, each agent's calls follow that agent's policy, not the most permissive one in the system, and everything lands in one audit trail.
All of it recorded in one hash-chained audit log, per agent, per team
Team-wise policies
Rules match on team, agent or app, data type and task, and the first matching rule decides. Give each team the protection its work needs instead of one policy that's too loose for some and too strict for others. Some examples:
Team · Clinical
Profile: HIPAA · Clinical
Team · Engineering
Profile: Coding agents & developer tools
Team · Customer support · EU
Profile: GDPR · EU personal data
Team · Finance
Profile: PCI DSS · Payments
Team · Marketing
Profile: Marketing & communications
Team · Data science
Profile: Evaluation & sandbox
Examples of rules you can set up. Rules are ordered, versioned with snapshots and rollback, and anything no rule allows is denied.
Audit everything
Nothing an agent does through agentKeyRoute goes unrecorded. Each request keeps its full decision trace: who or what sent it, what data was found, which rule applied, which model and account actually served it, what it cost and how long it took.
Changes to the rules are recorded too: policies, profiles, keys, providers, budgets and settings, along with who made them and who approved them. Support access is read-only and appears in your own log. Entries are hash-chained, and an integrity check shows if any were altered.
Anything that calls the OpenAI or Anthropic API can run through agentKeyRoute: Claude Code, Codex, Cursor, LangChain, the OpenAI and Anthropic SDKs, and agents you've built yourself. Change the base URL, give each agent its key, and it's governed.
Register your first agent, give it a key and a profile, and watch every step it takes in the request explorer.