One record per agent
Owner, role, purpose, permissions, model, data scopes, and status for every agent, including partner and customer-built ones registered through the Gateway.
Platform
Registry. Every agent in your enterprise. One record each.
One registry of every agent, whether built by Meridian, a partner, or your own team, with owner, role, permissions, data touched, and compliance status. Workforce analytics that count agents and people together.
app.meridian.example/registry
24 agents
AgentsPeopleFilter
| Agent | Owner | Compliance |
|---|---|---|
| Payroll Agent | M. Reyes | Compliant |
| Help Desk Agent | D. Okafor | Compliant |
| Audit Agent | K. Lindqvist | Compliant |
| Controls Agent | S. Bhatt | Review due |
| Close Agent | T. Nakamura | Compliant |
| Vendor Risk CheckStudio | P. Adeyemi | Paused |
| Expense AuditorPartner | L. Marsh | Compliant |
| Scheduling Agent | R. Castillo | Compliant |
What is the Registry?
An HRIS gives every employee a record: who they report to, what they are allowed to do, what they cost, when they were reviewed. Agents need the same thing. Without it, the third agent someone builds in a business unit is invisible to security, uncounted by finance, and unaccountable to anyone.
The Registry is that record. Each agent, from any source, is registered with an owner, a role, the permissions it holds, the systems and data it touches, its model configuration, and its compliance status. Every action any registered agent takes is written to the same immutable log. Deprovisioning an owner suspends their agents the same way it revokes their badge.
Because agents and people are recorded side by side, leaders can see workforce capacity honestly. The Registry reports hours saved, cases resolved, cost per outcome, and exception rates by agent, next to the human team's metrics, so return on investment is measured rather than asserted.
- Agents inherit identity from your IdP and roles from the source system; none has credentials of its own
- Every action by any registered agent lands in the same immutable, exportable log
- The Registry API exposes the same fields to your GRC, ITSM, and SIEM tools
- Owner offboarding through SCIM suspends the owner's agents within minutes
Capabilities
What Registry does
6 capabilities, each enforced below the agent so they apply to Meridian, partner, and Studio-built agents alike.
Permissions and data lineage
Agents hold no standing credentials. Each inherits scopes from your identity provider and the source system's security model. The Registry shows exactly which tables and documents each agent can read.
Compliance status
Review dates, risk tier, approved use cases, and evaluation results per agent. Agents that miss a review are flagged; agents that fail an evaluation can be paused automatically.
Blended workforce analytics
Hours saved, outcomes produced, credits consumed, and exception rates by agent, reported alongside human team metrics so capacity and ROI are measured on one page.
Lifecycle controls
Pause, resume, scope down, or retire any agent from one place. Owner offboarding suspends the agents that person owned until a new owner is assigned.
Cost attribution
Credits and model spend attributed to agent, workspace, and cost center. Export to your ERP or FinOps tooling.
Specification
Registry specification
Standards, protocols, and limits as of September 2026. Your account team can confirm coverage for a specific stack.
| Item | Specification |
|---|---|
| Record fields | Owner, role, purpose, permissions, model configuration, data scopes, risk tier, review dates, evaluation results, status |
| Agent sources | Meridian agents, partner agents registered through the Gateway, agents published from Studio |
| Action log | One immutable log for every registered agent; entries hashed and chained; exportable to SIEM or archive |
| Analytics | Hours saved, outcomes produced, credits consumed, and exception rates by agent, next to human team metrics |
| Lifecycle controls | Pause, resume, scope down, retire; owner offboarding through SCIM suspends that owner's agents within minutes |
| Integration | Registry API and scheduled exports for GRC, ITSM, SIEM, ERP, and FinOps tooling |
| Identity | Agents hold no standing credentials; scopes inherited from your IdP and the source system |
| Plan availability | Growth and Enterprise |
How it fits
How Registry fits the platform
One identity model, one policy layer, one log. The other components and the trust model that binds them.
Questions
Questions about Registry
It is a single, authoritative registry of every AI agent operating in an organization, recording for each one its owner, role, permissions, data access, model configuration, and compliance status, in the way an HRIS records employees. Meridian's Registry is an agent system of record that also captures every action each agent takes.
Yes. Partner agents and agents your developers build in other frameworks register through the Gateway using open protocols. Once registered they appear in the Registry with the same record structure, log, and controls as Meridian's agents.
Each agent reports the outcomes it produces (cases resolved, shifts filled, packages assembled) and the credits it consumes. The Registry applies your time-per-task and cost assumptions, which you can edit, and reports hours saved and cost per outcome next to human team metrics. Assumptions are visible on every chart.
Yes. Agent records, review status, and evaluation results are available through the Registry API and as scheduled exports. Design partners synced them to their GRC platforms as assets with control mappings.
Get started
Put the first agent to work this quarter.
Start with one workflow, one approver, and one number to move. Most design partners were live in five weeks.