Registry

The ACP Registry serves a narrow but critical niche: it's the official distribution channel for agents that speak the Agent Client Protocol, and the authentication requirement sets it apart from generic agent marketplaces. For developers building ACP clients, the programmatic CDN endpoint (curl https://cdn.agentclientprotocol.com/registry/v1/latest/registry.json) provides a machine-readable catalog with versioned metadata and distribution info, making agent discovery and installation automatable. For agent authors, the fork-based submission workflow on GitHub is straightforward and community-driven, with maintainers curating for quality and authentication compliance. The registry's strength is its focus: every listed agent supports authentication, which is a meaningful trust baseline for teams that need security-conscious tooling. It's also actively evolving with the protocol—recent stabilizations of boolean config options, request cancellation, session usage updates, and message IDs in ACP v1, plus the v2 draft, show a living ecosystem. However, this focus is also its limitation. If you're not working within ACP, the registry offers little value; it's not a general-purpose app store, and it doesn't provide AI models itself—it's an index. Non-technical users may find the GitHub-based workflow and CLI-oriented fetch model intimidating. The registry also doesn't offer SLA-backed support or paid tiers, which could be a concern for enterprise teams requiring formal support. For its intended audience—developers and teams embedded in the ACP ecosystem—it's an indispensable resource. For everyone else, it's a niche tool whose relevance depends entirely on the protocol's adoption. The recent news of ACP v2 draft publication and SDK 1.0 releases suggests momentum, but it's still early days.