{
 "acronym": "AIP",
 "adoption": {
  "by": null,
  "level": "unmeasured",
  "probe_run": null
 },
 "aliases": [],
 "analog": "W3C DID plus a delegated-capability credential chain",
 "collisions": [
  "Agent Interaction Protocol (unrelated proposals sometimes use the same AIP initialism)"
 ],
 "discovery": {
  "mechanism": "W3C Decentralized Identifier (DID) resolution plus cryptographic delegation-chain verification",
  "path": "none"
 },
 "dispute": {
  "claims": [
   "Author-declared 'Intended Status: Standards Track' does not itself confer IETF consensus or WG adoption; treat as aspirational until a WG picks it up."
  ],
  "summary": "This is a single-author draft with an author-stated Standards Track intent but no WG sponsorship and no located implementation; the acronym AIP is also used elsewhere for unrelated agent-interaction proposals, which is a collision worth flagging to readers."
 },
 "evidence": [
  {
   "claim": "AIP defines a decentralized identity, delegation and authorization framework for autonomous AI agents combining W3C DIDs, capability-based authorization, cryptographic delegation chains and deterministic validation, aiming to avoid reliance on centralized identity providers; it is a sole-author Internet-Draft (Paras Singla, Independent) with Standards Track as the author's intended status, and no working-group sponsorship, as shown on its ietf.org archive header",
   "date": "2026-06-10",
   "label": "REPORTED",
   "url": "https://www.ietf.org/archive/id/draft-singla-agent-identity-protocol-03.html"
  },
  {
   "claim": "The IETF Datatracker's document page for draft-singla-agent-identity-protocol shows Document Type 'Active Internet-Draft (individual)', RFC stream '(None)', Intended RFC status '(None)', and last updated 2026-06-09 -- confirming no working-group has taken up the draft.",
   "date": "2026-06-09",
   "label": "REPORTED",
   "url": "https://datatracker.ietf.org/doc/draft-singla-agent-identity-protocol/"
  }
 ],
 "form": "endpoint",
 "governance": "IETF individual draft; sole author, no working group",
 "group": null,
 "history": [
  {
   "date": "2026-09-05",
   "note": "seeded from Exa Agent research run"
  },
  {
   "date": "2026-09-06",
   "note": "verified against draft-singla-agent-identity-protocol-03's abstract, introduction and document header; flagged limited depth of review and the AIP acronym collision"
  }
 ],
 "id": "aip",
 "implementation": "none-found",
 "last_verified": "2026-09-06",
 "name": "Agent Identity Protocol (AIP)",
 "native_status": "Internet-Draft, Intended Status: Standards Track (author's stated intent; not adopted by any WG)",
 "origin": {
  "date": "2026-06-10",
  "org": "Paras Singla (Independent)"
 },
 "part_of": null,
 "parties": [
  "agent-agent"
 ],
 "phase": "draft",
 "probe": {
  "method": "n/a",
  "on_absent": "Absence of a site artifact means nothing; AIP is negotiated between agents.",
  "parse": "n/a",
  "path": "n/a (client-side protocol; no fixed origin artifact)"
 },
 "question": "How can an autonomous agent prove a decentralized identity and a verifiable chain of delegated authority from its human or organizational principal?",
 "scope": "general",
 "spec_url": "https://www.ietf.org/archive/id/draft-singla-agent-identity-protocol-03.html",
 "step": "identify",
 "summary_md": "The Agent Identity Protocol (AIP) is a proposed decentralized identity, delegation, and authorization framework for autonomous AI agents. It combines W3C Decentralized Identifiers (DIDs), capability-based authorization, cryptographic delegation chains, and deterministic validation, explicitly aiming to let multi-agent workflows be secure and auditable without depending on a centralized identity provider [1].\n\nIt targets the \"identity gap\" the author identifies: when an autonomous agent — which may send emails, book appointments, make purchases, access file systems, spawn child agents, or act across multiple platforms without per-action human approval — presents itself to an API, a payment processor, or another agent, there is today no standard way to establish the agent's persistent identity across interactions, which human or organization it acts on behalf of, or exactly which actions it is authorized to take [1]. AIP is not a working, deployed system: this pass reviewed the draft's abstract and introduction and did not verify the full delegation-chain wire format, so claims about a specific probeable endpoint or resolvable path cannot be made honestly at this time.\n\nCurrent state: draft-singla-agent-identity-protocol-03, published 2026-06-10, a sole-author IETF Internet-Draft under the Network Working Group umbrella (not a chartered WG) [2]. The author lists \"Standards Track\" as the intended status, but this is the author's own stated intent, not an indication of IETF working-group consensus or adoption — no WG has taken up this document as far as this check found [2].\n\nWho implements it: no implementation, reference library, or deployment was located in this pass.\n\nDisputed or unknown: whether AIP will be picked up by any chartered WG or remain an individual proposal; how it relates to, competes with, or could compose with ERC-8004's onchain identity model or ANS's DNS-anchored model (both also in this Identify layer) is not addressed in the reviewed text. The AIP acronym also collides with other unrelated agent-interaction proposals circulating in the same space, so readers should confirm they mean this specific draft.",
 "track": "community",
 "version": {
  "date": "2026-06-10",
  "label": "draft-singla-agent-identity-protocol-03, published 2026-06-10"
 },
 "url": "https://agenticweb.wiki/protocols/aip/",
 "category": "identify",
 "type": "protocol"
}