Readable
Basic website facts and machine-readable files exist.
Registry model
A registry is more than a list of profiles
A useful agent registry normalizes identity, capabilities, trust, transport, security, freshness and action limits. It should help agents classify and compare businesses without turning the hub into a Google-indexed SEO directory.
Documentation
Core fields
These are the fields AgntBase should normalize as A2A readiness grows.
| Identity | domain, company_name, canonical_profile_url, agent_card_url. |
|---|---|
| A2A readiness | a2a_version, supported_interfaces, skills, default_input_modes, default_output_modes. |
| Trust | signature_status, last_checked_at, freshness, verification_status, provenance. |
| Access | security_schemes, security_requirements, extended_card_available, allowed_actions. |
Documentation
Readiness statuses
Status labels make the registry operational instead of decorative.
Discoverable
Agent Card and standard entrypoints are reachable.
Trustable
Provenance, freshness, signatures or owner verification are present.
Actionable
Safe routes exist for booking, checkout, contact, forms or human review.
Gated
Extended capabilities require authentication or partner access.
Blocked
Homepage, files or card are blocked by anti-bot or server rules.
Documentation
Google-safe policy
The registry should help agents without looking like scaled SEO content abuse.
Index public education
Homepage, articles, trust pages, methodology and useful docs can be indexed.
Noindex registry layer
Large profile/hub layers can stay accessible to agents and APIs without inviting Google into a mass directory.
Quality gate
Profiles should be complete, sourced, deduplicated and useful before they become public machine-readable records.