Agent Registry

What is the registry?

The Agent Registry is a centralized catalog of every AI agent in your organization. It serves three core functions:

Inventory — discover and track all agents (internal and platform-managed)
Governance — assign owners, policies, and approval chains
Compliance — map agents to controls and standards

Whether your agents live in your repo, a SOAR platform, or a managed service, they all appear in one place with consistent metadata.

Discovery

During onboarding, Arx scans your environment and auto-discovers agents:

Custom agents — Python, Go, Node.js scripts from your repo
Platform agents — Slack bots, integrations, managed services
SOAR workflows — Splunk SOAR, Tines, Microsoft SOAR playbooks
Automations — Zapier, Make, workflow automations

Each discovered agent receives a registry entry with:

Owner assignment
Connector list and permissions
Risk classification
Compliance mapping
Last activity timestamp

Metadata

Each registry entry captures key facts about the agent:

id:              "triage_crowdstrike_01"
owner:           "priya@fortune100bank.com"
owner_team:      "Detection & Response"
environment:     "production"
status:          "active"
runtime:         "python 3.12"
last_executed:   "2025-04-19T14:32:10Z"
version:         "2.4.0"
repo_url:        "https://github.com/f100bank/agents/tree/main/triage"
changelog:       "https://..."

connectors:      6 (crowdstrike, okta, wiz, servicenow, splunk, slack)
policies:        2 (prod-express-approval, high-risk-dual-control)
soc2_controls:   22 mapped, 3 pending
nist_ai_rmf:     GOVERN, MAP, MEASURE
approvals_pending: 1
      

Ownership & responsibilities

Every agent has an assigned owner. Owners are responsible for:

Responding to approvals — reviewing high-risk action requests
Maintaining policies — updating connector permissions and blast radius
Compliance updates — keeping control mappings current
Version management — tracking releases and rollbacks

Arx notifies owners of new approval requests, policy violations, and compliance drift.

Search & filtering

Find agents by:

Owner

Show me all agents owned by priya@...

Environment

Filter by prod, staging, dev

Connector

Which agents use Splunk? CrowdStrike?

Status

Active, inactive, or flagged

Compliance

Missing controls or non-compliant

Risk

High-risk, high-velocity agents

Approval routing

When an agent's action requires approval, Arx automatically routes it to the right person based on the agent's registry entry:

Primary approver: the agent owner
Escalation: team lead or compliance manager
Final authority: CISO for critical changes

Routing rules are defined in the agent's policy. Override on a per-action basis if needed.