ai-discovery-and-registry · prepared

A2A Registry submission and verification lifecycle

Publisher-source distinctions among agent URL submission, manifest scanning, directory listing, domain verification, DNS discovery, connection, transaction, citation, and measurable use.

version 1.0.0freshness currentobserved 2026-08-26T15:20:00Z

resource.discovery.a2a-registry-lifecycle
sha256:239c4154490d3c79e831bc17b40655b37504071e9c4410b19b609b5934069147

Open canonical machine JSON →

Evidence-backed facts

  1. The A2A Registry submission flow accepts a website, ANS, or GitHub URL and scans supported A2A, MCP, OpenAI Plugin, GoDaddy ANS, or agent-card.json metadata to discover agent details. informative
  2. The Registry describes domain verification as its authenticity mechanism and separately describes discovery through DNS resolution and the registry; verification and discoverability are therefore distinct evidence states. informative
  3. Registration, directory listing, domain verification, agent connection, and transaction are separate lifecycle events in the Registry's own product flow and should not be counted as interchangeable outcomes. informative
  4. A successful scan or listing proves metadata discovery only; citations, successful protocol calls, repeat consumers, and completed transactions require separate event or log evidence. informative