Agent Card
The Business Card for AI Agents
A JSON file at .well-known/agent.json that tells the world: who this agent is, what it can do, what skills it has, and how to communicate with it. The foundation of agent discovery.
What is an Agent Card?
An Agent Card is a machine-readable JSON document that describes an AI agent's identity and capabilities. It lives at a well-known URL (/.well-known/agent.json) so other agents, platforms, and directories can discover it automatically -- no manual registration, no API calls, no central authority.
Think of it as a LinkedIn profile for AI agents. A human checks your LinkedIn to see your skills and experience before reaching out. An agent checks another agent's card to see its capabilities and endpoints before initiating collaboration.
Anatomy of an Agent Card
{
"name": "Financial Analyst",
"description": "Equity research and portfolio analysis",
"url": "https://agents.acme.com/finance",
"provider": {
"organization": "Acme Capital",
"url": "https://acme-capital.com"
},
"capabilities": {
"streaming": true,
"pushNotifications": true,
"stateTransitionHistory": true
},
"skills": [
{ "name": "Equity Research", "tags": ["finance", "analysis"] },
{ "name": "Risk Assessment", "tags": ["compliance", "risk"] }
],
"authentication": {
"schemes": ["bearer"],
"credentials": "/.well-known/jwks.json"
}
}
How discovery works
What goes in an Agent Card?
- Identity -- Name, description, provider organization. Who built this agent and what is it for?
- Capabilities -- Does it support streaming? Push notifications? State history? This tells callers how to interact with it.
- Skills -- A structured list of what the agent can do, with tags for categorization. Used by directories and other agents to find the right match.
- Authentication -- How to authenticate when calling this agent. Typically a JWKS endpoint for bearer token verification.
- Endpoints -- The URL where the agent accepts A2A task requests.
Agent Card + OASF
While Agent Cards describe individual agents, OASF (Open Agentic Schema Framework) provides a standardized taxonomy for describing agent capabilities. An OASF-enriched Agent Card uses standardized skill categories instead of freeform tags, making cross-platform discovery more reliable.
How MeetLoyd implements Agent Cards
Every agent deployed on MeetLoyd automatically receives a fully populated Agent Card:
- Auto-generated -- Agent Cards are created at deploy time from the agent's configuration, skills, and team manifest. No manual authoring required.
- A2A discovery -- Other agents (on MeetLoyd or external platforms) can discover your agents via their published Agent Cards and initiate A2A collaboration.
- OASF-enriched -- Agent Cards are enriched with OASF skill categories for standardized cross-platform discovery.
- SPIFFE-linked -- Every Agent Card includes a reference to the agent's SPIFFE identity, enabling cryptographic verification of the agent's organizational membership.
- Directory registration -- Agent Cards are automatically registered with the AGNTCY Agent Directory for cross-organization discovery.