Opening
Agentic Engineering Days Zurich / 20 November 2026
Agents
Speak
Protocol
Why standards are the
real infrastructure of AI
Stefano Maestri & Alessio Soldano
Opinions are our own and do not represent our employer.
Opening
We have worked on both sides of the boundary
The previous wave
Alessio
Soldano
Apache CXF / WS-*
RESTEasy / REST
Shared contractsThe 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
NetworksConnect
different systems
TCP/IP
ServicesAgree on
an interface
WSDL + SOAP
REST APIs
EditorsReuse
integrations
LSP
AgentsMeet 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?
Keep the contract. Change the implementation
The map
Standards emerge at different boundaries
What do you want to make replaceable?
Tools boundary
Every new tool multiplies the wiring
A shared interface changes the shape of integration
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
Agent CardMessages / TasksArtifacts
Agree on the work. Keep internals private
Agents boundary
A task can outlive a single response
Track work, exchange input, receive artifacts
Illustrative path / input-required is a pause, not completion
The architecture
Capability access + outcome delegation
MCP Invoke a capability
A2A Delegate an outcome
Other boundaries
The rest of the map
The user boundaryShow the work
AG-UI — events & shared state
A2UI — declarative components
MCP Apps — tool UI inside a host
The knowledge boundaryAgree on meaning
AGENTS.md — project instructions
Agent Skills — SKILL.md + resources
Agent Plugins — packaged reuse
The operations boundaryFollow 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
Agent Client Protocol ≈ the LSP pattern
Sessions / progress / permissions / cancellation
The bets
Adopt where replacement matters
Start from a needMCP
Reusable tool integrations
A2A
Independent agent delegation
Evaluate the contractCompatibility
Common subset
Extensions
Independent implementations
Keep the rest on your radarOne 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?