{
 "acronym": "AP",
 "adoption": {
  "by": "project README (lists Auto-GPT, Auto-GPT-Forge, and smol developer as adopters, with e2b and Auto-GPT as 'engaged' in protocol development)",
  "level": "claimed",
  "probe_run": null
 },
 "aliases": [
  "AI Engineer Foundation Agent Protocol"
 ],
 "analog": "a REST job-queue API for arbitrary autonomous-agent backends",
 "collisions": [
  "Agent Connect Protocol (AGNTCY)",
  "Agent Communication Protocol (IBM)",
  "Agent Client Protocol (Zed)"
 ],
 "discovery": {
  "mechanism": "None published; a client is expected to know an agent's base URL out of band (no well-known path or registry defined by the spec itself)",
  "path": null
 },
 "dispute": {
  "claims": [
   "agi-inc/agent-protocol README and repository 'About' field designate https://agentprotocol.ai/ as 'the docs'",
   "As fetched 2026-09-06, agentprotocol.ai serves a third-party comparison guide with no evident connection to AI Engineer Foundation, AGI Inc., or the agent-protocol repository"
  ],
  "summary": "The repository's own README and GitHub 'About' field link https://agentprotocol.ai/ as the project's documentation home, but as fetched during this verification pass the domain serves unrelated third-party content — a vendor-neutral protocol-comparison guide covering MCP, A2A, and Agent Protocol — with no visible affiliation to AI Engineer Foundation, AGI Inc., or the GitHub repository that links it. The canonical specification currently survives only as the openapi.yml file inside the GitHub repository itself."
 },
 "evidence": [
  {
   "claim": "The GitHub repository formerly at AI-Engineer-Foundation/agent-protocol now redirects to agi-inc/agent-protocol ('Maintained by AGI, Inc.'), MIT licensed, 1.5k stars, 186 forks; its README defines the protocol as an OpenAPI REST spec with POST /ap/v1/agent/tasks and POST /ap/v1/agent/tasks/{task_id}/steps as its two essential routes, and lists Auto-GPT, Auto-GPT-Forge, and smol developer as adopting projects.",
   "date": "2026-09-06",
   "label": "VERIFIED",
   "url": "https://github.com/AI-Engineer-Foundation/agent-protocol"
  },
  {
   "claim": "The repository's own 'Docs' link, https://agentprotocol.ai/, currently serves an unrelated third-party site ('AgentProtocol.ai') describing itself as 'an independent, vendor-neutral guide' comparing MCP, A2A, and Agent Protocol — it shows no visible affiliation with AI Engineer Foundation, AGI Inc., or the agi-inc/agent-protocol repository, and does not host the project's own documentation.",
   "date": "2026-09-06",
   "label": "VERIFIED",
   "url": "https://agentprotocol.ai/"
  }
 ],
 "form": "endpoint",
 "governance": "Originated as an AI Engineer Foundation (AIEF) community project (GitHub org formerly AI-Engineer-Foundation); the repository now lives under 'agi-inc' and states it is 'Maintained by AGI, Inc.', a commercial entity; the docs domain linked from the repository, agentprotocol.ai, currently serves unrelated third-party content rather than AIEF/AGI Inc. project documentation",
 "group": null,
 "history": [
  {
   "date": "2026-09-06",
   "note": "added from arXiv 2504.16736 survey comparison, verified against github.com/AI-Engineer-Foundation/agent-protocol (redirects to agi-inc/agent-protocol), agentprotocol.ai"
  }
 ],
 "id": "agent-protocol-aief",
 "implementation": "multi-implementation",
 "last_verified": "2026-09-06",
 "name": "Agent Protocol",
 "native_status": "\"Common interface for interacting with AI agents. The protocol is tech stack agnostic\" (repository description); defined as an OpenAPI REST spec with two core routes, POST /ap/v1/agent/tasks and POST /ap/v1/agent/tasks/{task_id}/steps",
 "origin": {
  "date": null,
  "org": "AI Engineer Foundation (AIEF), originally alongside the Auto-GPT/e2b community"
 },
 "part_of": null,
 "parties": [
  "agent-site"
 ],
 "phase": "draft",
 "probe": {
  "method": "POST",
  "on_absent": "A 404 or schema mismatch means this origin does not implement Agent Protocol. Given the project's docs domain has since been repurposed to unrelated content and no commit activity was found in the past year, absence should now be treated as the default expectation rather than a surprise.",
  "parse": "A 200/201 response returning a Task object containing a task_id field confirms an Agent-Protocol-compliant server per the OpenAPI schema.",
  "path": "{origin}/ap/v1/agent/tasks"
 },
 "question": "How does a client or dev-tool start a task on an autonomous agent, step it, and fetch results, regardless of which framework built the agent?",
 "scope": "general",
 "spec_url": "https://github.com/AI-Engineer-Foundation/agent-protocol",
 "step": "act",
 "summary_md": "Agent Protocol is a framework-agnostic, OpenAPI v3 REST specification originally proposed by the AI Engineer Foundation (AIEF) community, alongside the early Auto-GPT/e2b ecosystem, to give any autonomous agent a single, predictable interface: create a task (POST /ap/v1/agent/tasks), execute it step by step (POST /ap/v1/agent/tasks/{task_id}/steps), and list or download artifacts, regardless of the framework the agent was built with [1]. It solves the comparison and integration problem for early agent frameworks — before Agent Protocol, every agent exposed a bespoke interface, making benchmarking and devtool-building across agents difficult; the spec's own stated goal is 'great developer experience' for agent builders wanting to avoid writing boilerplate API code [1].\n\nIt does not define agent-to-agent communication (the README lists this as future roadmap, unrealized), does not define authorization on behalf of end users, and does not define discovery — clients are expected to know an agent's base URL out of band [1].\n\nAs of this check (September 2026), the project's governance and web presence show significant drift from its AIEF origins. The GitHub repository formerly hosted under the AI-Engineer-Foundation organization now redirects to agi-inc/agent-protocol and states it is \"Maintained by AGI, Inc.,\" a commercial entity, rather than the original community foundation [1]. More notably, the repository's own linked documentation domain, agentprotocol.ai, no longer hosts the project's docs at all: as fetched during this verification pass, it serves an unrelated third-party site describing itself as an 'independent, vendor-neutral guide' to MCP, A2A, and Agent Protocol, with no visible connection to AI Engineer Foundation, AGI Inc., or the GitHub repository that links to it as its official documentation [2]. This is flagged as a dispute rather than treated as settled, since it was not possible in this pass to determine whether the domain lapsed and was independently re-registered, or was deliberately repurposed by a current stakeholder.\n\nImplementation history shows genuine multi-party adoption during the 2023–2024 Auto-GPT era — Auto-GPT, Auto-GPT-Forge, and smol developer all merged Agent-Protocol-compliant PRs, with e2b and Auto-GPT credited as 'engaged' co-developers of the spec — but no evidence of continued active development or adoption was found in the past year of repository activity [1]. What is unresolved: whether Agent Protocol should be considered a live, maintained standard at all today, or a historically important but now largely dormant spec whose primary surviving artifact is the OpenAPI file in a repository under new, commercial ownership.",
 "track": "single-vendor",
 "version": {
  "date": null,
  "label": "unversioned OpenAPI spec (schemas/openapi.yml)"
 }
}