Identity fields
name, description, version, provider and documentation URL.
The current A2A discovery object is the Agent Card. For AgntBase, it is not a marketing page. It is structured capability, security, version and skill metadata that agents can use before deciding whether and how to interact.
A useful Agent Card explains who the agent is, what it can do, how to reach it, and what security rules apply.
name, description, version, provider and documentation URL.
supportedInterfaces should show transport URLs and preferred modes, not just a vague endpoint.
skills, default input modes and output modes tell clients what the agent can actually handle.
A public card should not leak private capabilities, but it should say how protected operations are accessed.
OAuth, OpenID Connect, API keys, mTLS or other schemes can be declared as machine-readable requirements.
Different skills or operations may require different scopes, auth state or client privileges.
A public card can point toward richer authenticated capability detail without exposing everything publicly.
This is the first practical validation pass we can apply to public business and agent interfaces.
| Reachability | Does /.well-known/agent-card.json return a readable JSON document? |
|---|---|
| Shape | Does it include identity, prioritized supportedInterfaces, skills and documentation signals? |
| Trust | Is it versioned, signed where needed, fresh, linked from the website and consistent with the canonical profile? |
AgntBase uses several machine-readable files, but they do different jobs.
company-profile.json | The compact canonical business profile: identity, services, contacts, trust signals and owner-approved facts. |
|---|---|
agenthub.json | AgntBase hub entrypoint: points the client website to the canonical hub profile and related protocol files. It is not an A2A Agent Card. |
/.well-known/agent-card.json | The A2A Agent Card: public agent-facing capability, interface, security and skills metadata for agent-to-agent discovery. |