A useful system can distinguish the person, service, or agent taking an action; the party it represents; and the permission for that action. Treating all three as one shared secret makes a later decision harder to explain.
Before automating a task, ask three separate questions: who is acting, on whose behalf, and within which permission. This is a practical way to review delegation without reducing it to a token or an API key.
A DID is an identifier that lets others resolve a relationship to its controller. A verifiable credential is a signed claim from an issuer. Neither one replaces every account, login flow, or permission rule; together they make those roles easier to state precisely.
Use the DID and credential pages for the concepts; the historical articles below document earlier public work on decentralized identity, not a promise about every current integration.
How a durable identifier connects to authorization, revocation and audit.
Agents Need an Identity. DID May Be the Best Place to StartInspect did:abt role types and how identifiers are derived.
Understanding DIDs