Public layer
Canonical profile, llms.txt, company-profile.json, agenthub.json, and Agent Card.
A2A + MCP
A2A connects agents. MCP connects tools.
A2A and MCP solve different problems. MCP gives an agent access to tools, resources and context. A2A lets agents communicate and coordinate with other agents. AgntBase sits around discovery, identity, trust and business-readable profiles.
Documentation
The simple distinction
This framing keeps product decisions clean and prevents the common market confusion.
| MCP | Agent-to-tool and agent-to-resource integration. Useful for internal capabilities, data, actions and context. |
|---|---|
| A2A | Agent-to-agent communication, discovery, task exchange and capability negotiation. |
| AgntBase | Identity, registry, trust, canonical profiles, verification and readiness checks for business-facing agent interfaces. |
Documentation
Why both matter for a business
A future business interface may expose public facts, gated actions and internal tools at different levels.
Gated layer
Authenticated extended Agent Card with more capabilities, stricter auth and partner-only detail.
Tool layer
MCP-backed internal tools for stock, booking, CRM, checkout or support once access is granted.
Documentation
Product decision
AgntBase should not pretend every small business needs a full A2A agent on day one.
Phase 1
Make the business readable and verifiable.
Phase 2
Expose agent discovery and safe handoff rules.
Phase 3
Add real agent actions only where the business can keep data, prices and permissions current.