Agent Identity Protocol (AIP) AIP
Agent Identity Protocol (AIP) is an agentic-web standard (endpoint) at step 2, Identify, governed by IETF individual draft; its status is "Internet-Draft, Intended Status: Standards Track". It answers: "How can an autonomous agent prove a decentralized identity and a verifiable chain of delegated authority from its human or organizational principal?" Implementation status is none found, last verified 2026-10-29.
Identify The Agent Identity Protocol (AIP) is a proposed decentralized identity, delegation, and authorization framework for autonomous AI agents. It combines W3C Decentralized Identifiers (did:aip, derived from an agent's Ed25519 key), capability-based authorization (Capability Manifests), cryptographic delegation chains with scope attenuation (default depth 3, hard cap 10), an AIP-GRANT consent ceremony, and a Registry that issues short-lived signed Credential Tokens and DPoP-bound OAuth 2.0 tokens via RFC 8693 token exchange for MCP servers [1].
Overview
It targets the "identity gap" the author identifies: when an autonomous agent 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].
Current state: draft-singla-agent-identity-protocol-03, published 2026-06-10 (expiring 2026-12-12), a sole-author IETF Internet-Draft by Paras Singla under the Network Working Group umbrella (not a chartered WG) [2]. The author lists "Standards Track" as the intended status, which reflects the author's stated intent rather than IETF working-group adoption [2].
Who implements it: no implementation, reference library, or deployment was located.
Disputed or unknown: whether AIP will be picked up by any chartered WG or remain an individual proposal. The AIP acronym and did:aip method name also collide with other proposals (draft-prakash-aip and a Solana-based did:aip entry in the W3C DID method registry), so readers should confirm they mean this specific draft.
Discovery and probe
W3C Decentralized Identifier (DID) resolution plus cryptographic delegation-chain verification · none
n/a n/a (client-side protocol; no fixed origin artifact) parse: n/a on absent: Absence of a site artifact means nothing; AIP is negotiated between agents.
Instances
No instances recorded yet.
See also
- Pairs with: ERC-8004: Trustless Agents, Agent Name Service v2 (ANS), Agent Authorization Grant, Workload Identity in Multi System Environments (WIMSE), Model Context Protocol
- Not to be confused with: Agent Interaction Protocol (unrelated proposals sometimes use the same AIP initialism), did:aip Solana-based DID method in the W3C DID method registry, Agent Identity Protocol (Prakash, draft-prakash-aip / arXiv 2603.24775)
References
- 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 — https://www.ietf.org/archive/id/draft-singla-agent-identity-protocol-03.html (2026-06-10) REPORTED
- 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. — https://datatracker.ietf.org/doc/draft-singla-agent-identity-protocol/ (2026-06-09) REPORTED
Disputed: 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.
Verification log and errata
- — verified against draft-singla-agent-identity-protocol-03's abstract, introduction and document header; flagged limited depth of review and the AIP acronym collision
Frequently asked questions
- What is Agent Identity Protocol (AIP)?
- Agent Identity Protocol (AIP) is an agentic-web standard (endpoint) at step 2, Identify, governed by IETF individual draft; its status is "Internet-Draft, Intended Status: Standards Track". It answers: "How can an autonomous agent prove a decentralized identity and a verifiable chain of delegated authority from its human or organizational principal?" Implementation status is none found, last verified 2026-10-29.
- What is the adoption and standardization status of Agent Identity Protocol (AIP)?
- Internet-Draft, Intended Status: Standards Track (author's stated intent; not adopted by any WG), governed by IETF individual draft; sole author, no working group. Implementation: none found. Version: draft-singla-agent-identity-protocol-03, published 2026-06-10 (2026-06-10). Last verified 2026-10-29.
- How does Agent Identity Protocol (AIP) compare to other identify protocols?
- Agent Identity Protocol (AIP) is one of 22 standards at step 2, Identify (Who is this agent? Who is this site?). It pairs with ERC-8004: Trustless Agents, Agent Name Service v2 (ANS), Agent Authorization Grant, Workload Identity in Multi System Environments (WIMSE). Every standard at this step is listed at https://agenticweb.wiki/category/identify/.