Agent Registry
The Agent Registry holds one record for each agent that can bind the company. It works as a signing authority register for software. The sample board resolution in the Corporate Authority for Agents guide names an officer to maintain it. Update it whenever a mandate, credential or status changes, and keep earlier versions, so you can show what authority any agent held on any past date.
| Field | What it holds | Example: Acme procurement agent |
|---|---|---|
| Agent ID | The identifier the agent uses with systems and counterparties | acme-procurement-agent-01 |
| Principal | The legal entity whose position the agent affects | Acme Corp. |
| Provider | Who supplies or runs the agent’s software, if not the company, and under which agreement | [Provider name], under the agreement dated [date] |
| Regulatory role | For each use, which party is the provider and which the deployer under any AI law that applies, and whether any use is high-risk | [Provider name] is the provider and Acme the deployer; no use is high-risk |
| Business owner | The individual accountable for the agent’s activity | Procurement manager |
| Legal owner | The lawyer responsible for the agent’s mandate and contracts | [Name], Legal |
| Purpose and authority level | What the agent is for, and its level (0 Recommend to 4 Execute within limits) | Order servers and networking hardware; level 4 |
| Irreversible acts | Acts the agent can take that can’t be undone, and the check on each | Check each card payment and purchase order against the mandate before sending it. Block orders above $10,000. For otherwise permitted orders, require approval above $5,000, on the first order with a vendor, or on the first order under the applicable Agent Transaction Addendum, even with an existing vendor. |
| Mandate | The current version of the signed Agent Mandate and where it is kept | Agent Mandate v2, signed by the Director of IT Procurement and the Chief Financial Officer, in the contracts system |
| Approved by | Who approved the mandate, and under which delegation | Director of IT Procurement, under the delegation of authority policy; also the Chief Financial Officer, because the agent may make card payments and authenticate purchase orders |
| Limits | The main limits, in summary | $10,000 per order; $50,000 per month in total and $20,000 per vendor; approved vendors only |
| Subagents | Whether the agent may delegate, and to what | Not permitted |
| Credentials | Each credential the agent holds, and who issued it | OAuth client (IT); virtual card ending [xxxx] (Finance) |
| Counterparties told | Which counterparties have the agent’s limits in writing, and in which version | Vendors that signed the Agent Transaction Addendum; Schedule A v1, drawn from Agent Mandate v2 |
| Start and end dates | When the agent’s authority starts and ends | Oct. 1 to Dec. 31, 2026 |
| Status | Active, suspended or revoked, with the date of the last change | Active |
| Revocation | How to revoke the agent, and who can | Kill switch run by IT; notice to vendors and the card issuer, prepared and held by Procurement |
| Records | Where the agent’s logs are kept, and for how long | Provider console and Acme archive. Keep transaction evidence for at least six years and preserve evidence under a legal hold. Remove identifiable details once no longer needed, even within six years. |
| Last reviewed | When the mandate was last checked against the live system | [date] |
Related: Corporate Authority for Agents · Agent Mandate · Ending authority