agentmesh · cards and descriptors
Each agent, harness and mesh has one signed descriptor, and its card is made from it.
The Common Agent Specification already works this way for the agent: the Agent Descriptor is the authored, signed source, and the agent card is made from it, never edited on its own. AgentMesh applies the same rule to the harness and the mesh.
three documents each
Each thing has a descriptor, a card and a record.
| Thing | Descriptor: authored and signed | Card: made from it, for finding it | Record: attested, what runs |
| Agent | What it offers, refuses, needs and leaves behind | /{agent}/.well-known/agent-card.json | The deployment record |
| Harness | The agents it hosts, what co-hosted agents share, its session boundary | A harness card listing each agent and its card | The deployment record |
| Mesh | Owning organization, goals, services, rules it enforces, members, who may visit | /.well-known/mesh-card.json | Servers, regions and capacity, mostly private to the operator |
examples
Here is an example harness card and an example mesh card.
A host can run many agents, and A2A has no standard way to ask which, or what they can reach of each other. The harness card answers both. The mesh card carries only what a newcomer needs to reach the mesh; goals, counter goals, constraints and membership rules stay in the Mesh Descriptor.
Harness card
// GET https://agents.example.com/.well-known/harness-card.json
{
"harness": "agents.example.com",
"session_boundary": "per-session sandbox",
"shared_in_session": ["files", "context"],
"not_shared": ["credentials"],
"agents": [
{ "name": "brand-analytics",
"card": "/brand-analytics/.well-known/agent-card.json" },
{ "name": "reputation",
"card": "/reputation/.well-known/agent-card.json" },
{ "name": "slides",
"card": "/slides/.well-known/agent-card.json" }
],
"descriptor": "/harness-descriptor.json"
}
Mesh card
// GET https://marketing.example.com/.well-known/mesh-card.json
{
"mesh": "marketing.example.com",
"organization": "example.com",
"key": "ed25519:9fX2...",
"transports": ["agent-messaging", "a2a-https"],
"join": "invite",
"visit": "one-hour pass, admission screened",
"services": {
"registry": "/a2m/registry",
"rooms": "/a2m/rooms",
"board": "/a2m/board",
"memory": "/a2m/memory",
"goals": "/a2m/goals"
},
"descriptor": "/mesh-descriptor.json"
}
following the chain
A caller can follow an agent's name to its mesh's rules.
An agent's name resolves to its card, and its card names its home mesh. The mesh card leads to the Mesh Descriptor, so a caller can learn a mesh's rules and how it admits visitors before it sends anything.
name→agent card→ its home mesh →mesh card→Mesh Descriptor