Agent-to-Business

AI agents need control before execution.

A2B is an AI agent governance protocol with a reference implementation architecture. It defines how an agent proves who it is, how policy decides what it may do before execution, and how the outcome is preserved as durable evidence.

The problem

  • Agents gain access to email, CRM, billing, files and infrastructure.
  • Prompts alone do not create reliable authorization boundaries.
  • Risky actions may execute before a human can intervene.
  • Logs often show intent, but not a trustworthy chain of decisions and outcomes.

The A2B response

  • Identify the agent and its permitted scope.
  • Evaluate policy before any business side effect.
  • Require human approval where the policy demands it.
  • Record the decision and actual outcome as durable evidence.

The core invariant

Identity → Policy-before-execution → Immutable Ledger

1

Identity

The system knows which agent is requesting an action, for whom it acts, and which capabilities it holds.

2

Policy before execution

Every proposed action is evaluated before it reaches the target system: allow, deny, or require approval.

3

Immutable Ledger

The request, decision, approval and actual result are preserved in a tamper-evident, reviewable trace.

What A2B can govern

The protocol applies wherever an agent can create a business side effect.

Customer-facing actions

Email sends, support replies, CRM updates and scheduling proposals.

Control before an agent affects a customer or business record.

Data and tool access

Reads, writes, exports and tool calls constrained by identity and scope.

Explicit boundaries around what an agent may access and change.

High-impact operations

Destructive, financial or infrastructure actions that need stronger policy and approval.

A reviewable decision path before irreversible execution.

Protocol and product are not the same thing

A2B is the umbrella protocol and architecture. A2B Operator is the first hosted product being built to expose its policy, approval and traceability controls through a usable interface and API.

Private preview

Current status

The concept, documentation and implementation work are active. Operator is not presented here as a finished public SaaS subscription.

View the Operator direction →

Follow the work as it develops

Read the implementation notes and review the public code as the protocol becomes a working control product.