Aegis Runtime — AI authority infrastructure

Your agents can act. We define how far.

The AI Action Envelope™ gives every autonomous agent a bounded, enforced authority — checked at the moment it acts, not just described in a policy document.

Sits in front of agents already built on
OpenAIAnthropicCopilot Studio LangChainCrewAIMCP Custom Python / Java
Customer Refund Agent · runtime check refund.issue
$4,000 requested amount
$0$400$5,000$6,000+
decisionREQUIRE_APPROVAL
reasonExceeds the autonomous limit of $400, but within the approval ceiling of $5,000. Routed to the nominated approver.
executedno — pending approval
A dashboard tells you what an agent did. Aegis Runtime decides whether it's allowed to happen at all — before the action reaches your systems.
Enforcement runs in the request path, not in a report generated afterward.
how it works

We don't replace your agent. We sit between it and what it's allowed to touch.

Every action request passes through the gateway before it reaches a business system — evaluated against the agent's registered authority in real time.

01
Client's AI agent
→
02
AI Action Envelope™
→
03
Aegis Gateway
→
04
Risk & policy evaluation
→
05
Approve, deny or execute
→
06
Business system
agent authority

Governance applies to specific actions, not vague access levels.

Each tool an agent can call has a stable identity — refund.issue, customer.lookup, ledger.delete — so authority can be granted and denied precisely.

Customer Refund Agent — permitted tools

✓Look up customer
✓Check order status
✓Check refund eligibility
✓Issue refund

Denied by default

✗Delete customer
✗Modify accounting ledger
✗Export customer database
✗Change payment details
Action Envelope — Customer Refund Agent v3
allowed actions
Check refund eligibility · Issue customer refund
restrictions
  • Maximum autonomous refund: $400
  • Maximum refund requiring approval: $5,000
  • Refunds above $5,000: deny
  • Approved customer accounts only, no bulk refunds
  • Production access only
validity
1 Sept 2026 – 30 Sept 2026
owner / approver
Customer Operations / Finance Governance
getting started

From first registration to production enforcement.

Every agent moves through the same guided path — nothing reaches production until its envelope has been reviewed.

01

Set up your organisation

Create the workspace and invite the administrators who'll own registration and approvals.

02

Register the agent

Name it, assign a business and technical owner, and state its purpose and environment.

03

Assess its risk

Aegis Risk runs a guided questionnaire — financial impact, data sensitivity, reversibility, blast radius — and produces a risk profile.

04

Define the envelope

Set permitted actions, financial limits, approval thresholds and validity dates.

05

Simulate before enforcing

Run the envelope against real traffic first: "this would have blocked 17 actions, and required approval for 6."

06

Activate and monitor

Turn on production enforcement, route approvals, and revisit the risk rating as the agent's role changes.

what you see

One place to see every agent's authority — and every decision it made with it.

Aegis Registry4 agents
AgentRiskStatus
Customer Refund AgentHIGHActive
HR Information AssistantMEDIUMActive
Internal Knowledge AgentLOWActive
Supplier Payment AgentCRITICALSuspended
Aegis Approvals2 pending
Refund request #1042$4,000
Customer Refund Agent · triggered "approval ceiling" rule · expires in 3h 12m
Supplier payment #883$12,000
Supplier Payment Agent · triggered "above autonomous limit" rule · expires in 22h
Aegis Auditsearchable
  • Agent registration
  • Risk assessments
  • Envelope creation & changes
  • Policy decisions
  • Approved actions
  • Denied actions
  • Suspensions
  • Human approvals
  • Actual executions
  • Failed executions
  • Authority violations
connecting an agent

Three ways in, depending on how the agent is built.

01 · SDK

Python SDK

pip install governance-kernel

from governance_kernel import GovernedGateway

gateway = GovernedGateway(
  agent_id="finance-refund-agent",
  api_key="client-issued-key"
)

result = gateway.execute(
  action="refund.issue",
  arguments={
    "customer_id": "customer-123",
    "amount": 4000
  }
)
The most direct path for Python-based agents.
02 · API

Hosted gateway

POST /v1/agents/finance-refund-agent/actions

{
  "action": "refund.issue",
  "amount": 4000,
  "customer_id": "customer-123"
}

← {
  "decision": "REQUIRE_APPROVAL",
  "request_id": "req-1042",
  "reason": "Amount exceeds
    autonomous limit"
}
Works for agents written in any language.
03 · MCP

Governed tool endpoint

// The agent sees an ordinary
// MCP tool.
//
// Every invocation is routed
// through the enforcement
// layer first — no change
// to the agent's own
// reasoning loop.
Governs MCP-connected agents without touching how they think.
pricing

A base platform fee, plus the scale of what you enforce.

Priced on governed AI actions evaluated by the gateway, not on the number of agents you register — so consolidating agents to save money is never the incentive.

PILOT
Small teams and pilots
A$10,000–25,000illustrative, per year
  • Up to 5 registered agents
  • Development & staging environments
  • Basic Action Envelopes
  • Standard audit history
  • Email support
Start a pilot
BUSINESS
Production departmental use
A$40,000–100,000illustrative, per year
  • More agents & environments
  • Production enforcement
  • Risk Registry & human approvals
  • SSO and role-based access
  • Extended audit retention
Talk to sales
ENTERPRISE
Regulated or large organisations
A$150,000+illustrative, per year
  • High-volume enforcement
  • Private or dedicated deployment
  • Advanced identity integration
  • Custom policy & integrations
  • Security reviews & SLAs
Request briefing

These ranges are illustrative starting points, not confirmed pricing — final packages are scoped against your agent count, environments and approval workload.

Put bounded authority around your first AI agent.

Aegis Runtime is currently onboarding selected design partners. Work with us to define an AI Action Envelope™, integrate your agent, simulate its authority boundaries, and move toward controlled enforcement.