{
 "acronym": "ACP",
 "adoption": {
  "by": null,
  "level": "unmeasured",
  "probe_run": null
 },
 "aliases": [
  "AConP",
  "ACP (AGNTCY)"
 ],
 "analog": "a REST API gateway for invoking a remote service",
 "collisions": [
  "Agent Client Protocol (Zed)",
  "Agent Communication Protocol (IBM)",
  "Agentic Commerce Protocol (OpenAI/Stripe)"
 ],
 "discovery": {
  "mechanism": "An agent's ACP capabilities are described in an 'ACP descriptor' retrievable via the ACP interface itself or embedded in that agent's record in an AGNTCY agent directory (now superseded in AGNTCY's active tooling by the 'dir' project); no site-wide well-known path is defined",
  "path": "/agents/search"
 },
 "dispute": null,
 "evidence": [
  {
   "claim": "The agntcy/acp-spec GitHub repository ('Agent Connect Protocol Specification', Apache-2.0, 168 stars) was archived by the owner on 2026-04-11 and is now read-only; its last commit was 2025-05-23 (PR #46, adding basic type support for input/output/config).",
   "date": "2026-09-06",
   "label": "VERIFIED",
   "url": "https://github.com/agntcy/acp-spec"
  },
  {
   "claim": "The rendered OpenAPI spec at spec.acp.agntcy.org (v0.2.3, OpenAPI 3.1.1) defines the Agents, Threads, Thread Runs, and Stateless Runs operation groups (POST /agents/search, GET/POST /threads, POST /runs, etc.) for invoking and configuring remote agents.",
   "date": "2026-09-06",
   "label": "VERIFIED",
   "url": "https://spec.acp.agntcy.org/"
  },
  {
   "claim": "The AGNTCY GitHub organization currently lists 49 public repositories with activity within hours to days of this check, with its identity/discovery focus now centered on the 'dir' (Distributed Announce and Discovery of Multi-Agentic-Systems) and 'oasf' (Open Agentic Schema Framework) projects rather than acp-spec.",
   "date": "2026-09-06",
   "label": "VERIFIED",
   "url": "https://github.com/orgs/agntcy/repositories"
  }
 ],
 "form": "endpoint",
 "governance": "AGNTCY project (Cisco donated AGNTCY to the Linux Foundation); the acp-spec GitHub repository was archived by its owner (the agntcy GitHub organization) on 2026-04-11 and is now read-only, while the broader AGNTCY project (49 repositories, most recently updated within hours of this check) remains active under Linux Foundation governance, with its discovery/identity work now centered on the 'dir' (Distributed Announce and Discovery) and OASF (Open Agentic Schema Framework) projects rather than acp-spec",
 "group": "Protocols called ACP",
 "history": [
  {
   "date": "2026-09-06",
   "note": "added from arXiv 2504.16736 survey comparison, verified against github.com/agntcy/acp-spec, spec.acp.agntcy.org, github.com/orgs/agntcy/repositories"
  },
  {
   "date": "2026-09-06",
   "note": "governance corrected to reflect Cisco donating AGNTCY to the Linux Foundation, per sibling records ads/oasf/slim; verified against existing agenticweb.wiki records"
  }
 ],
 "id": "agent-connect-protocol",
 "implementation": "deprecated",
 "last_verified": "2026-09-06",
 "name": "Agent Connect Protocol (AGNTCY)",
 "native_status": "OpenAPI 3.1.1 specification, version 0.2.3; source repository archived (read-only) by the owner on 2026-04-11; the rendered interactive spec at spec.acp.agntcy.org still resolves and is unchanged since its last update in May 2025",
 "origin": {
  "date": "2025-02",
  "org": "Cisco / LangChain, published under the AGNTCY Collective"
 },
 "part_of": null,
 "parties": [
  "agent-agent"
 ],
 "phase": "deprecated",
 "probe": {
  "method": "POST",
  "on_absent": "A 404 or non-JSON response means no ACP server at this origin. Because the specification's own source repository was archived by its owner in April 2026 with no announced successor, absence is the expected and increasingly common result over time.",
  "parse": "A 200 response returning a JSON array of agent objects (each with agent_id and metadata.ref) confirms an ACP-speaking server per the v0.2.3 OpenAPI schema.",
  "path": "{origin}/agents/search"
 },
 "question": "How does one agent (or an orchestrator) invoke and configure a remote agent it did not build, over a plain HTTP API?",
 "scope": "general",
 "spec_url": "https://github.com/agntcy/acp-spec",
 "step": "act",
 "summary_md": "The Agent Connect Protocol (ACP), published by the AGNTCY Collective (co-founded by Cisco and LangChain), defines a standard REST/OpenAPI interface for invoking and configuring a remote agent over an API — covering agent discovery/search, stateless Runs, stateful Thread Runs with checkpointed state history, and streaming output [1][2]. It targets the same problem the Agent Client Protocol (Zed) and IBM's now-retired Agent Communication Protocol both address — a standard invocation surface for interchangeable agents — but is a third, independently governed specification that also happens to be commonly abbreviated \"ACP,\" a collision the AGNTCY project shares with at least two other unrelated \"ACP\" specifications tracked on this map [1].\n\nACP does not itself define agent-to-agent negotiation or a payments layer; its scope is narrowly the client/orchestrator-to-agent invocation surface, with agent metadata for richer discovery deferred to a separate 'agent directory' concept. It also does not define transport beyond HTTP/REST — there is no WebSocket or message-queue binding in the specification.\n\nAs of this check (September 2026), the specification's source repository (agntcy/acp-spec) was archived by its owner on 2026-04-11 and is now read-only, with its last substantive commit dated 2025-05-23 [1]. The rendered interactive OpenAPI documentation at spec.acp.agntcy.org still resolves and is served unchanged since that date, so existing implementations can still consult it, but no further spec development is occurring under this repository [2]. The broader AGNTCY Collective remains highly active — 49 public repositories with commits as recent as hours before this check — but its current discovery and identity work is concentrated in newer projects ('dir', a distributed agent directory, and 'oasf', the Open Agentic Schema Framework) rather than in acp-spec, suggesting AGNTCY's own architecture has moved on from this component without a formal deprecation notice or migration guide comparable to IBM's ACP-to-A2A banner [3].\n\nGovernance was, and nominally remains, the AGNTCY Collective's open, multi-vendor structure (Apache 2.0 license, public GitHub PR process, 'Copyright AGNTCY Contributors'). What is unresolved: whether any production deployments still run ACP servers independently of the newer 'dir'-based tooling, and whether AGNTCY intends to formally retire or fold ACP's invocation surface into a successor — no such announcement was found during this verification pass, only the archival action itself.",
 "track": "linux-foundation",
 "version": {
  "date": "2025-05-23",
  "label": "v0.2.3 (OpenAPI 3.1.1)"
 },
 "url": "https://agenticweb.wiki/protocols/agent-connect-protocol/",
 "category": "act",
 "type": "protocol"
}