# Agent Identity Protocol (did:aip, Singla draft) AIP

[2 · Identify](/category/identify/)
Candidate · auto-drafted, unreviewed · confidence 60%

| Agent Identity Protocol (did:aip, Singla draft) |
| --- |
| Category | [Identify](/category/identify/) |
| Governed by | Individual author's IETF Internet-Draft; no working group adoption stated on the page |
| Status | Internet-Draft; the did:aip DID method is "requested for registration" with status Draft (Section 22.1) |
| Phase | draft |
| Implementation | none found |
| Adoption | unmeasured |
| Version | Draft (version not stated; before v1.0 minor versions may break compatibility) |
| Specification | [https://insights.bostonidentity.com/research/ietf-datatracker-2026-04-17-agent-identity-protocol-aip](https://insights.bostonidentity.com/research/ietf-datatracker-2026-04-17-agent-identity-protocol-aip) |
| Found at | A principal's did:aip DID document names its Registry; the Registry holds a versioned Trust Record and issues credential tokens |
| Acronym collisions | aip, did:aip Solana-based DID method in the W3C DID method registry, Agent Identity Protocol (Prakash, arXiv 2603.24775) |
| Last checked | 2026-10-19 |
| Freshness | current · checked 2026-10-19 |
| Solves | Prove an agent's identity, Delegate a user's authority to an agent, Audit what an agent did |

Agent Identity Protocol (did:aip, Singla draft) is an agentic-web standard (document format) at step 2, Identify, governed by Individual author's IETF Internet-Draft; its own status is "Internet-Draft; the did:aip DID method is "requested for registration" with status Draft (Section 22.1)" (draft). It answers: 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? Adoption is unmeasured, last verified 2026-10-19.

[Identify](/category/identify/) 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.

## Discovery and probe

A principal's did:aip DID document names its Registry; the Registry holds a versioned Trust Record and issues credential tokens

```
NONE
parse:
on absent: No site-level probe is defined; support cannot be observed from a well-known path.
```

Not probed live: no-fixed-path. candidate record; probe rule pending

## History
- 2026-10-19 — auto-drafted candidate from exa (https://insights.bostonidentity.com/research/ietf-datatracker-2026-04-17-agent-identity-protocol-aip)

## Instances

No instances recorded yet.

## See also

- Not to be confused with: aip, did:aip Solana-based DID method in the W3C DID method registry, Agent Identity Protocol (Prakash, arXiv 2603.24775)

## References

- 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. — [https://insights.bostonidentity.com/research/ietf-datatracker-2026-04-17-agent-identity-protocol-aip](https://insights.bostonidentity.com/research/ietf-datatracker-2026-04-17-agent-identity-protocol-aip) (2026-10-16) REPORTED

[JSON](/data/protocols/agent-identity-protocol-singla.json) · [Markdown](/protocols/agent-identity-protocol-singla/index.md)