Verified identity
Give the agent a unique, organization-approved identity tied to its runtime or credential. A name supplied by the caller is a claim; a verified identity can anchor policy and evidence.
Strategy and architecture
The agentic economy will start inside enterprises. Learn how identity, human ownership, scoped authority, approvals, and evidence form its control plane.
Updated Jul 20, 2026
The first agentic economies are already forming inside enterprises, where agents delegate work, access systems, recommend terms, and trigger consequential actions. Before organizations give them more economic authority, every agent needs a verified identity, a human owner, scoped authority, approval boundaries, and a system of record.
The agentic economy is an economy in which software agents do more than answer questions. They discover options, coordinate with other agents, choose a path, allocate time or money, and complete work on behalf of people and organizations. A transaction may be a card payment, but it may also be a purchase order, a refund, a contract renewal, an access grant, a cloud deployment, or a promise made to a customer.
The useful dividing line is not whether an agent has a wallet. It is whether the agent can create an obligation. The moment software can commit a budget, change a system of record, select a supplier, or delegate a task that ends in one of those outcomes, it is participating in economic activity.
The demand signal is already visible. Adobe measured traffic from generative AI sources to US retail sites rising 693.4% year over year during the 2025 holiday season. Those referrals also converted 31% more often than non-AI traffic. This is not proof that autonomous agents completed every purchase; it is evidence that AI is rapidly becoming part of how economic intent reaches a merchant.
The World Economic Forum frames the trust problem directly: identity and accountability infrastructure will determine whether agentic commerce creates prosperity or a new fraud surface. Its proposed Know Your Agent model asks four questions that enterprises also need internally: what is the agent, what may it do, for whom is it acting, and how is its behavior monitored?
Adobe AI traffic report, January 2026 · World Economic Forum: AI agents, identity, and accountability
The popular image is a personal agent roaming the open internet, negotiating with merchant agents and paying on its owner's behalf. The nearer-term economy is less cinematic and more important: agents inside companies already work inside known processes, with access to CRM, ERP, ticketing, identity, cloud, and procurement systems. They have counterparties, budgets, managers, policies, and consequences.
Microsoft's May 2026 Work Trend Index reported 15x year-over-year growth in active agents across the Microsoft 365 ecosystem, rising to 18x in large enterprises. The same report says IT should treat agents as managed entities with identities, permissions, policy enforcement, and lifecycle management, and explicitly describes IT as the control plane for agent operations.
Adoption is moving faster than the operating model. Deloitte surveyed 3,235 business and technology leaders in 24 countries and found that only 21% described their agentic AI governance as mature. Yet 74% expected their organizations to use agents at least moderately by 2027. Deloitte identified the missing capabilities in concrete terms: autonomy boundaries, human approval rules, real-time monitoring, and audit trails across the full chain of actions.
That gap is why enterprise comes first. A company can define authority before two unknown agents meet in an open market. It already knows the department that owns the budget, the person accountable for the process, the systems the agent may touch, and the approval policy for an exception. The enterprise is the first place where an agent can receive meaningful economic authority and the first place where that authority can be governed.
Microsoft 2026 Work Trend Index · Deloitte: agentic AI is scaling faster than guardrails
Traditional software executes a path someone designed. An agent can interpret a goal, choose among paths, ask another agent for help, and adapt before it acts. That does not make the agent a legal person, and it does not transfer accountability away from the organization. It does change what must be controlled.
A useful actor test is to ask what the software can change without another human click. The more boxes it checks below, the less useful it is to govern it as a generic application or shared service account.
| Capability | Tool behavior | Economic-agent behavior | Control question |
|---|---|---|---|
| Choice | Returns options to a person. | Selects an option or counterparty. | Which choices are inside its charter? |
| Resources | Calculates or displays a price. | Commits budget, compute, inventory, or staff time. | What limit applies to this action now? |
| Commitment | Drafts a message or document. | Sends, signs, orders, refunds, grants, or changes. | When must a human authorize the commitment? |
| Delegation | Calls a fixed API. | Asks a sub-agent or external agent to complete the goal. | What authority travels with the task? |
| Adaptation | Follows a predefined branch. | Renegotiates its plan as conditions change. | Which change requires re-approval? |
An enterprise does not need to predict every action an agent might take. It needs a small set of controls that remain legible as the agent changes plans, tools, and counterparties. These five controls turn an autonomous workflow into accountable delegation.
Give the agent a unique, organization-approved identity tied to its runtime or credential. A name supplied by the caller is a claim; a verified identity can anchor policy and evidence.
Name the business owner who can approve the charter, change boundaries, stop the agent, fund remediation, and answer for outcomes. Keep technical ownership alongside it, not instead of it.
Define permitted tools, data, action types, counterparties, environments, budgets, time windows, and delegation paths. Authority should be narrow enough to evaluate at runtime.
Allow routine actions, deny forbidden ones, and pause exceptions for the correct role. Add quorum, separation of duties, deadlines, fallback owners, and safe timeout behavior where the risk requires them.
Record the parent request, every handoff, policy result, human decision, trusted resume signal, and final outcome in one durable timeline. The record must follow the work, not one framework.
Agent identity · How to choose an AI agent owner · System of record for AI agents · Best AI agent control plane tools
A control plane should not replace the agent runtime, identity provider, policy engine, observability stack, ERP, or payment network. It coordinates the decision boundary between them. The runtime proposes an action; identity establishes the actor; policy evaluates the scope; the control plane allows, pauses, or denies; and the system of record preserves the full decision and outcome.
The architecture matters because policy on paper cannot interrupt a tool call. The control plane must sit close enough to the action to enforce the result before the external side effect occurs, while remaining independent enough that every framework and department follows the same authority model.
| Plane or system | Primary job | Signal passed to the next layer |
|---|---|---|
| Agent runtime | Reason, plan, call tools, and delegate work. | Proposed action plus context and delegation chain. |
| Identity and inventory | Resolve the specific agent, owner, lifecycle status, and credentials. | Verified actor and organizational relationship. |
| Policy and authority | Evaluate scope, risk, counterparty, environment, and limits. | Allow, deny, or require a named decision path. |
| Decision operations | Route approval, enforce quorum and SLA, escalate, and return a trusted result. | Signed or otherwise verifiable decision to resume or stop. |
| System of record | Join identity, request, policy, delegation, decision, callback, and outcome. | Searchable, exportable evidence for operations and audit. |
Procurement is no longer a hypothetical use case. SAP announced agentic capabilities spanning sourcing, bid analysis, negotiation strategy, purchasing, policy management, and automated purchase-order creation in 2026. That is exactly where the line between software assistance and economic agency becomes visible: the agent moves from finding information to shaping and executing a commercial commitment.
Imagine a department asks its procurement agent to source replacement equipment. The agent translates the request into requirements, delegates supplier discovery to a specialist, compares compliant offers, asks an external supplier agent to improve delivery terms, and prepares the purchase. A well-designed control plane does not interrupt every step. It intervenes when authority changes.
| Moment | Agent action | Control-plane decision |
|---|---|---|
| Request | Turns a business request into specifications and evaluation criteria. | Bind the task to the requester, budget owner, purpose, and policy. |
| Discovery | Delegates supplier search and collects offers. | Allow read-only delegation to approved sources; record each handoff. |
| Negotiation | Requests better price, delivery, or warranty terms from an external agent. | Constrain the negotiable fields and prevent disclosure outside approved data. |
| Selection | Ranks a supplier and explains the choice. | Check approved-vendor policy, conflicts, and material deviations from intent. |
| Commitment | Prepares or submits the purchase order. | Route to the accountable budget or procurement owner when policy requires approval. |
| Execution | Sends the order and records confirmation. | Resume only on a trusted decision; attach the outcome and receipt to the same record. |
SAP: autonomous spend management with agents · SAP: agentic procurement and automated purchase orders
Contro1 gives every agent a place in the organization before it gets more autonomy. Agents appear in an inventory with verified or claimed identity, owner, framework, hierarchy, scopes, and activity. Teams can tighten authority or block an agent instead of relying on a display name or a shared service credential.
At runtime, consequential actions become governed decisions. Contro1 receives the action and context, applies the organizational route, sends the request to the correct role, department, shift, manager, policy owner, or approval hierarchy, tracks the SLA, escalates when nobody responds, and returns a signed callback before the agent resumes.
The same thread becomes the system of record: acting agent, parent and sub-agent traces, proposed action, policy context, human decision, callback, and final outcome. Low-risk actions can remain autonomous and land as audit-only records. High-impact actions receive legible friction exactly where the organization has decided that human authority must remain visible.
| Enterprise question | Contro1 control |
|---|---|
| Which agent is acting? | Verified and claimed identities in Agent Inventory. |
| Who owns it? | Named business owner, technical context, hierarchy, and fallback ownership. |
| What may it do? | Scopes, permissions context, action boundaries, and block controls. |
| Who decides the exception? | Role-based routing, shifts, quorum, approval hierarchy, SLA, and escalation. |
| Can the agent trust the answer? | Signed callback and idempotent resume pattern. |
| Can we prove the full chain? | Linked requests, traces, decisions, outcomes, and HMAC-signed evidence exports. |
Agent identity · AI agent ownership · System of record for AI agents · Control plane comparison
Do not begin with a committee trying to govern an imaginary economy. Begin with one agent that already has the power to create a real obligation. The first implementation should make the authority chain visible end to end and give the organization a pattern it can reuse.
Find one action that sends, spends, changes, grants, deletes, or commits the organization. Start at the side effect, not at the prompt.
Assign the business person who already owns the outcome and the technical person who owns implementation. Do not make a generic AI committee the fallback.
Write what the agent may do autonomously, what is forbidden, and which changes in amount, counterparty, scope, or environment require review.
Capture identity, delegation, policy, decision, trusted resume, and outcome in one thread. If the evidence fragments at a handoff, fix the handoff.
The agentic economy is the emerging system in which AI agents discover options, coordinate with other agents, allocate resources, and complete consequential actions on behalf of people and organizations. It includes payments, but also purchase orders, refunds, access changes, deployments, bookings, and other business commitments.
Enterprises already give agents access to workflows, systems, budgets, policies, and counterparties. They also have the organizational ingredients needed to govern that authority: owners, approval roles, risk limits, identity systems, and systems of record. That makes internal agent operations the first practical agentic economy.
It is the operational layer that connects agent identity, human ownership, scoped authority, policy, approvals, escalation, trusted resume signals, and audit evidence. It decides whether a consequential action may proceed and preserves the reason and outcome.
No single protocol replaces one. A2A standardizes agent collaboration and task delegation. UCP standardizes commerce journeys, while AP2, Visa TAP, and Verifiable Intent add important identity, intent, and authorization signals. The enterprise must still decide who may delegate authority, what the agent may do, when a human must approve, and who owns the outcome.
Authority should travel with the task as explicit, machine-readable scope and should usually narrow at each handoff. The record should preserve the original principal, owner, purpose, limits, delegation chain, policy decisions, and outcome. A sub-agent should never gain more authority simply because it received a task.
No. Identity proves which agent is acting. Authority proves what that agent is allowed to do for this organization, in this context, at this moment. A trustworthy operating model needs both, plus a human owner, decision boundaries, and traceable outcomes.
Contro1 provides the enterprise operational layer: agent inventory and identity, named ownership, scoped authority, role-based approvals, shifts, quorum, SLA escalation, signed callbacks, linked traces, and evidence of the final outcome across agent frameworks.