INTENT-BASED INTER-AGENT COMMUNICATION PROTOCOL
IICP
An open protocol for choosing AI providers
through public rules
Roble Mumin
IETF / DISPATCH introduction ∙ 14 August 2026
•iicp.network
THE PROBLEM
Every agent action includes a provider choice
Agents call tools, delegate work, and reach
local or remote services. Before they act, an
application or platform chooses a provider and
a route.
That choice is usually hard-coded or
platform-specific.
An open system needs a way
to choose across compatible
providers without rebuilding the
same logic in every application.
Source: IICP Overview, August 2026; IICP directory and client architecture.
•roblemumin.com 2
•iicp.network
WHERE IICP FITS
A clear role beside other AI standards
MCP
connects AI tools and context
A2A
coordinates work between
agents
APIs
connect applications to ser-
vices
IICP understands the need, applies ca-
pability and policy rules, and selects an
eligible provider. The provider then uses
a connection method both sides support.
Source: IICP standards crosswalk, 31 July 2026, refreshed against the August 2026 protocol landscape.
•roblemumin.com 3
•iicp.network
THE SELECTION FLOW
Describe the need before choosing the provider
HARD-CODED
Call a named provider before checking which services meet the need.
INTENT-BASED
Declare a registered capability and constraints; discover and select among eligible providers.
Intent→discovery→eligibility→selection→execution
Source: IICP core, directory, and semantics…打开文档引用此文档