Canonical profile
Create an owner-approved profile with identity, services, trust, contacts, limits and next actions.
Implementation
Start readable. Then become discoverable, trustable and actionable.
Most small businesses do not need a full autonomous agent immediately. They need a clean first layer: official facts, files, profile, crawler access, and a route to the right action. A2A readiness can be added in phases.
Documentation
Phase 1 - readable
Make the business understandable before exposing complex actions.
Website files
Publish company-profile.json, llms.txt, AgntBase agenthub.json entrypoint and structured data. Keep this separate from the A2A Agent Card.
Placement check
Verify public access, robots rules, status codes and file quality.
Documentation
Phase 2 - discoverable
Add the current A2A discovery path when the business has an agent-facing interface or clear action surface.
Agent Card
Publish /.well-known/agent-card.json with identity, supported interfaces, skills and docs.
Registry listing
List the domain and card in AgntBase with status, freshness and validation results.
Transport metadata
Show preferred interface, endpoint URL, version and supported modes.
Documentation
Phase 3 - trustable
Move from a readable file to a verifiable object.
Sign the card
Use signatures when the ecosystem and implementation are ready.
Separate access tiers
Keep public facts public and richer capabilities behind authenticated extended cards.
Monitor reads
Track AI bots, status codes, failed reads and real access to entrypoint files.
Documentation
Phase 4 - actionable
Only add actions where the business can maintain current data and safe handoff.
| Allowed actions | Booking, checkout, quote request, contact form, messenger handoff or human review. |
|---|---|
| Owner responsibility | Prices, stock, services, policies and terms must stay current. |
| Payment rule | For small merchants, route agents to the merchant-owned checkout/payment page unless a trusted direct integration exists. |