Agent card
Concept
בפרוטוקול A2A, כרטיס סוכן (agent card) הוא מסמך הניתן לקריאה על ידי מכונה, המפורסם בכתובת מוכרת מראש, ומתאר את שמו של הסוכן, יכולותיו, כישוריו, נקודת הקצה שלו, דרישות האימות שלו ופורמטי הקלט והפלט שלו, כך שסוכנים אחרים יוכלו לגלות אותו.
נושאים שנדונים גם
בפרקים על Agent card עולים גם: Microsoft Purview Information Barriers, Context window, Front matter, Agent kill switch, AI red teaming ו-AI Center of Excellence.
Description
An agent card is a machine-readable document used in the Agent2Agent (A2A) protocol to describe an agent. It is published at a well-known URL and carries metadata such as the agent's name, description, version, capabilities, skills, endpoint, authentication requirements and the input and output formats it supports. Its core purpose is discovery: a client or another agent can read the card to learn what an agent offers before sending any request to it.
The A2A protocol addresses interoperability between agents by emphasizing a standardized language, which removes the need for custom code in each agent-to-agent interaction. The agent card is the part of that approach that lets an agent advertise its identity and capabilities. Instead of hard-coding assumptions about a remote agent, a calling agent reads the published card and works out how to reach the agent and what kinds of data it can exchange.
The Microsoft Learn page on A2A hosting in the Microsoft Agent Framework shows how this looks in practice. In the ASP.NET Core hosting example, the card is served at a well-known path ending in agent-card.json. The mapping method that exposes the card comes from the A2A SDK package rather than from the Agent Framework hosting packages. The sample card sets a name, a description and a version, default input and output modes, and a supported interface that includes a URL, a protocol binding and a protocol version. The page recommends that the card be fully populated for production use, so that clients receive complete information about the agent they are about to call.
A practical limitation described in the documentation concerns hosting. A single host can publish only one agent card at the well-known path, which means only one agent is discoverable there. Other agents hosted alongside it remain reachable through their own URLs, but clients must already know those endpoints, since the shared well-known location does not list them. When planning a deployment with several agents, this affects how discovery is designed and how endpoint information is shared with consumers. The documentation page does not cover skills, authentication details or card signatures, so those aspects of the card are described here only at the level of the general definition.
The episode "Agent-to-Agent (A2A) Communication - Simply Explained" touches on the concept as part of a wider discussion of interoperability. It presents the agent card as the mechanism through which agents advertise their identity and capabilities, making discovery and interaction easier. The same episode connects this to structured communication, where agents exchange various types of data, which supports collaboration and the tracking of task state. It also stresses that privacy and security concerns are central in agent-to-agent communication, and that anyone working with these systems should be aware of the risks associated with data handling. Because an agent card publishes information about an agent and how to reach it, deciding what to include and how access is controlled is part of that broader security consideration.
In summary, the agent card functions as the public description of an A2A agent. It is read by clients before any task is sent, it is served from a predictable location, and it should be complete and accurate in production. Its single-card-per-well-known-path constraint in the ASP.NET Core hosting example is a design point to account for whenever more than one agent is exposed from the same host.
Overview compiled with AI from M365.FM episodes and the facts on this page. You can improve it with the edit button below.
| Type | Concept |
|---|---|
| Kind | Format |
Community wiki
Short info above, community knowledge below: add practical tips, examples or corrections. New contributions are reviewed first; trusted members publish directly.
Experts and companies for this topic
Nobody has listed this topic yet. Add it to your profile.
Maintained by Mirko Peters (Microsoft MVP) · Last updated: