Opening

Agentic Engineering Days Zurich / 20 November 2026

Agents
Speak
Protocol

Why standards are the
real infrastructure of AI

CoverAn agent connects to models, tools, other agents, users, an IDE and context through separate boundaries.AGENTModelsToolsAgentsUsersIDEContext
Opening

We have worked on both sides of the boundary

The previous wave

Alessio
Soldano

Apache CXF / WS-*
RESTEasy / REST

Shared contracts

The current wave

Stefano
Maestri

A2A Technical Steering Committee
Linux Foundation

Independent agents

Our agents need to talk to other people's systems

History

Different decade, familiar integration problem

Networks

Connect
different systems

TCP/IP

Services

Agree on
an interface

WSDL + SOAP
REST APIs

Editors

Reuse
integrations

LSP

Agents

Meet the
same problems

Models / tools / peers

Move repeated decisions into a shared contract

History

A lens for this talk

The simplest protocol
that reduces the most
uncertainty wins

How many decisions disappear from the application?

The thesis

What can we replace without rewriting the agent?

ReplaceThe application and shared interface stay fixed while implementation A changes to implementation B.Your applicationIntegration staysShared contractBoundaryImplementation AReplaceable sideImplementation BSame interfaceKEEPKEEPSWAP

Keep the contract. Change the implementation

The map

Standards emerge at different boundaries

MapThree primary boundaries: models through Open Responses, capabilities through MCP, counterparts through A2A. Five additional boundaries: users, knowledge, operations, IDE, payments.ModelsOpen ResponsesCapabilitiesMCPCounterpartsA2AAGENTUsersAG-UI / A2UIKnowledgeFiles / Skills / PluginsOperationsOTel GenAIIDEACPPaymentsx402

What do you want to make replaceable?

Tools boundary

Every new tool multiplies the wiring

WiringThree applications and four capabilities: twelve pairwise integration surfaces compared with seven endpoints around a shared interface. This is an idealized count, not development cost.N × MN + MApp 1App 2App 3Tool 1Tool 2Tool 3Tool 43 × 4 = 12 integration surfacesMCPApp 1App 2App 3Tool 1Tool 2Tool 3Tool 43 + 4 = 7 protocol endpoints

A shared interface changes the shape of integration

Tools boundary

MCP gives capabilities a common interface

McpAn AI host owns model, policy and user experience. Its MCP client connects to a server that exposes primitives and adapts an existing domain API.HOST / AI APPLICATIONUser / policyModelMCP clientMCPMCP serverTools / resources / promptsDomain APILogs / deploys

Expose the capability once. Reuse the integration

JSON-RPC 2.0 / stdio or Streamable HTTP

Tools boundary

Three primitives, three control patterns

Tools

Act

Model typically selects

Read service errors
Resources

Know

Application supplies context

Service topology
Prompts

Start

User selects a template

Investigate an incident

The host retains policy and consent

From access to delegation

Same incident. A different request

“Read the latest
payment errors”

“Investigate the payment failure
and send me a diagnosis”

Who owns the work on the other side?

Agents boundary

A2A addresses an independent counterpart

A2AThe incident coordinator addresses a remote payments agent. An Agent Card describes the endpoint. Model, tools and memory remain internal to the payments team.Client agentIncident coordinatorA2APAYMENTS TEAM / OWN BOUNDARYRemote agentOwns the diagnosisAgent CardDiscoveryInternal implementationModel / tools / memory
Agent CardMessages / TasksArtifacts

Agree on the work. Keep internals private

Agents boundary

A task can outlive a single response

TaskIllustrative A2A task: submitted, working, input-required. The client supplies more input, the task resumes working and completes with a diagnosis artifact.submittedworkinginput-required“Correlation ID?”Client supplies inputcompletedDiagnosis + evidenceArtifact

Track work, exchange input, receive artifacts

Illustrative path / input-required is a pause, not completion

The architecture

Capability access + outcome delegation

TogetherThe incident coordinator accesses logs through MCP and delegates a diagnosis to a payments agent through A2A. The remote agent can use MCP for its own tools. Each integration crosses a different boundary.Incident agentYour applicationLogs / deploysMCP serverMCPA2APAYMENTS TEAMPayments agentOutcome: diagnosisPrivate model / context / strategyPayments toolsMCP

MCP Invoke a capability

A2A Delegate an outcome

Other boundaries

The rest of the map

The user boundary

Show the work

AG-UI — events & shared state

A2UI — declarative components

MCP Apps — tool UI inside a host

The knowledge boundary

Agree on meaning

AGENTS.md — project instructions

Agent Skills — SKILL.md + resources

Agent Plugins — packaged reuse

The operations boundary

Follow the work

OpenTelemetry GenAI — one trace across model, tools and delegation

Instrument and propagate at each boundary / pin the convention version

Smaller agreements, the same pattern

Opening a channel is not the agreement — WebSockets vs polling, all over again

IDE boundary

Change the coding agent, keep the editor

AcpAgent Client Protocol separates editor integration from coding agent implementation. Compatible agent A can change to agent B while the editor keeps the shared interface.Your editorDevelopment experienceACPAgent Client ProtocolCoding agent ACompatible implementationCoding agent BCompatible implementationKEEP THE CLIENTSWAP THE AGENT

Agent Client Protocol ≈ the LSP pattern

Sessions / progress / permissions / cancellation

The bets

Adopt where replacement matters

Start from a need

MCP

Reusable tool integrations

A2A

Independent agent delegation

Evaluate the contract

Compatibility

Common subset
Extensions
Independent implementations

Keep the rest on your radar

One boundary
at a time

Introduce a standard when
the integration pain is real

On the radar: x402 — the reserved HTTP 402 status gets a machine-readable payment contract

Closing

We have seen this before

Replace what is
on the other side.
Keep your applicationAgent

That is when a protocol becomes infrastructure

Discussion

Grazie! Questions?

Which boundary
hurts in your system?

Stefano Maestri
maeste.it

Alessio Soldano
aladinodigitale.it

Sources & further reading · Extended deck (35')

QR to maeste.it/speaking/agents-speak-protocol-aed.html
Slides & feedback
maeste.it/speaking/
agents-speak-protocol-aed.html