A2A ProtocolA2A Project · agent-communicationvs
AGNTCYAGNTCY · agent-communication
Two Linux-Foundation-era agent protocols. A2A standardizes task exchange and Agent Cards between agents; AGNTCY (Cisco-originated) aims at the whole 'Internet of Agents' stack — directory, SLIM messaging, identity, observability.
agentlist.io · documented attributes · sources and dates shown per value
Compare the same attributes
Every entry uses the same category fields. Open a source to check the scope and date behind a value. Not documented means we have no supported value, not that a feature is absent.
| Attribute | A2A ProtocolAwaiting documentation review | AGNTCYAwaiting documentation review |
|---|---|---|
| Common attributesDirectory metadata and source-documented values. Not documented is an evidence gap, not a negative claim. | ||
| CategoryAgentlist's buyer category; directory classification rather than a product capability. | Protocols and interoperability | Protocols and interoperability |
| Entry typeDirectory classification distinguishing products, frameworks, infrastructure and protocols. | protocol | infrastructure |
| Directory coverageHow the entry entered this directory; not a quality rating or a claim that every field is verified. | Cataloged | Cataloged |
| Recorded availabilityAvailability classification in the directory; check the source and review date before relying on current access. | active | active |
| InterfacesDocumented ways a person or application interacts with the entry. | Not documentedRecorded sourcesRecorded catalog specification; availability and terms may have changed. | Not documented |
| Execution / hostingWhere the documented service or workload runs; this is not a data-residency guarantee. | Not documentedRecorded sourcesRecorded catalog specification; availability and terms may have changed. | Not documented |
| Pricing basisSource-described price and billing basis. Different units and plans are not directly equivalent. | Not documentedRecorded sourcesRecorded catalog specification; availability and terms may have changed. | Not documented |
| LicenseDocumented license for the specified component or offering. | Not documented | Not documented |
| Protocols and interoperabilityComparable questions for this category. Sources and dates describe the evidence; no performance ranking is implied. | ||
| Agent interoperabilityImplements an agent interoperability protocol. | Not documented | Not documented |
| MCP supportDocumented MCP client or server support; consult scope for the role. | Not documented | Not documented |
| Protocol purposeThe interaction standardized by this protocol. | Not documented | Not documented |
| TransportsTransport bindings defined by the cited version. | Not documented | Not documented |
| Specification versionVersion of the cited specification, not a claim of latest status. | Not documented | Not documented |
| Authorization modelAuthorization mechanisms defined by the cited specification. | Not documented | Not documented |
Pick which
pick A2A Protocol if
You want the protocol with the widest vendor adoption signal (Google, IBM, Microsoft, Salesforce ecosystems) and a narrow, implementable scope.
pick AGNTCY if
You need the fuller stack — discovery directory and messaging fabric, not just a task-exchange schema.
watch out
The two overlap and both are young — expect convergence rather than a clean winner; avoid baking assumptions deep into application code.
Feature notes
- A2A Protocol
- 01Agent Cards for capability discovery
- 02Task lifecycle and artifacts
- 03Streaming updates
- 04Vendor-neutral governance (Linux Foundation)
- 05Composes with MCP
- AGNTCY
- 01Agent directory
- 02SLIM messaging fabric
- 03Identity and badges
- 04Observability SDKs
- 05Linux Foundation project
Frequently asked
A2A Protocol or AGNTCY — which should I pick?
Two Linux-Foundation-era agent protocols. A2A standardizes task exchange and Agent Cards between agents; AGNTCY (Cisco-originated) aims at the whole 'Internet of Agents' stack — directory, SLIM messaging, identity, observability. Pick A2A Protocol if: You want the protocol with the widest vendor adoption signal (Google, IBM, Microsoft, Salesforce ecosystems) and a narrow, implementable scope. Pick AGNTCY if: You need the fuller stack — discovery directory and messaging fabric, not just a task-exchange schema.
Is A2A Protocol or AGNTCY cheaper?
A2A Protocol: Open protocol (free). AGNTCY: Free (OSS, Apache-2.0). These are recorded catalog prices, not a fresh quote. Check vendor pricing for current plans, usage charges and seat terms.
Does A2A Protocol or AGNTCY run locally?
A2A Protocol hosting: local, cloud. AGNTCY hosting: local, cloud. Interfaces differ too: A2A Protocol exposes api, AGNTCY exposes api.
Are A2A Protocol and AGNTCY still maintained?
Recorded catalog status — A2A Protocol: actively maintained. AGNTCY: actively maintained. Check the linked sources for current availability; the catalog's creation date is not a product verification date.