{
 "id": "agent-identity-protocol-singla",
 "name": "Agent Identity Protocol (did:aip, Singla draft)",
 "acronym": "AIP",
 "aliases": [
  "did:aip",
  "AIP-GRANT"
 ],
 "collisions": [
  "aip",
  "did:aip Solana-based DID method in the W3C DID method registry",
  "Agent Identity Protocol (Prakash, arXiv 2603.24775)"
 ],
 "step": "identify",
 "parties": [
  "agent-site",
  "agent-registry"
 ],
 "form": "document-format",
 "track": "ietf",
 "scope": "general",
 "question": "How can an agent get a registry-anchored did:aip identity with a signed capability manifest and a delegation chain back to a person or organisation, which relying parties and MCP servers can check and revoke?",
 "analog": "DID method plus OAuth 2.0 token exchange (RFC 8693) for agents",
 "origin": {
  "org": "Paras Singla (independent)",
  "date": "2026-04-17"
 },
 "governance": "Individual author's IETF Internet-Draft; no working group adoption stated on the page",
 "native_status": "Internet-Draft; the did:aip DID method is \"requested for registration\" with status Draft (Section 22.1)",
 "phase": "draft",
 "implementation": "none-found",
 "adoption": {
  "level": "unmeasured",
  "by": null,
  "probe_run": null
 },
 "version": {
  "label": "Draft (version not stated; before v1.0 minor versions may break compatibility)",
  "date": null
 },
 "spec_url": "https://insights.bostonidentity.com/research/ietf-datatracker-2026-04-17-agent-identity-protocol-aip",
 "discovery": {
  "mechanism": "A principal's did:aip DID document names its Registry; the Registry holds a versioned Trust Record and issues credential tokens",
  "path": null
 },
 "probe": {
  "method": "NONE",
  "path": "",
  "parse": "",
  "on_absent": "No site-level probe is defined; support cannot be observed from a well-known path."
 },
 "evidence": [
  {
   "claim": "Boston Identity's IAM Insights briefing reports that the draft defines did:aip identifiers, a Registry, Capability Manifests, EdDSA-signed Credential Tokens, delegation chains with attenuation, an AIP-GRANT ceremony and Approval Envelopes. It also reports that no deployment or implementation is named, and that the draft's claim of W3C did:aip registration conflicts with its IANA-section statement that registration is only requested.",
   "label": "REPORTED",
   "url": "https://insights.bostonidentity.com/research/ietf-datatracker-2026-04-17-agent-identity-protocol-aip",
   "date": "2026-10-16"
  }
 ],
 "summary_md": "Draft by Paras Singla that defines did:aip, a DID method whose identifiers derive from an agent's Ed25519 key, with a Registry that issues short-lived signed Credential Tokens. It also covers Capability Manifests, delegation chains with scope attenuation (default depth 3, hard cap 10), revocation and an AIP-GRANT consent ceremony. For MCP servers the Registry acts as an OAuth server and issues DPoP-bound tokens by RFC 8693 token exchange. A third-party briefing reports that Tier 2 scopes require live Registry revocation checks, and that the did:aip name collides with another project's registered method.",
 "part_of": null,
 "group": null,
 "candidate": true,
 "confidence": 0.6,
 "use_cases": [
  "prove-agent-identity",
  "delegate-user-authority",
  "audit-agent-actions"
 ],
 "audience": [
  "agent-builder",
  "platform",
  "standards-body"
 ],
 "pairs_with": [
  "mcp",
  "wimse"
 ],
 "prerequisites": [],
 "dispute": null,
 "last_verified": "2026-10-19",
 "history": [
  {
   "date": "2026-10-19",
   "note": "auto-drafted candidate from exa (https://insights.bostonidentity.com/research/ietf-datatracker-2026-04-17-agent-identity-protocol-aip)"
  }
 ],
 "watch": [
  {
   "type": "page",
   "url": "https://insights.bostonidentity.com/research/ietf-datatracker-2026-04-17-agent-identity-protocol-aip"
  }
 ],
 "freshness": "current",
 "url": "https://agenticweb.wiki/protocols/agent-identity-protocol-singla/",
 "category": "identify",
 "type": "protocol"
}