Kamil Potrec describes how agents use personal tokens, model API keys and service accounts, and why these patterns make it hard to determine who authorized an action. He uses an invoicing example to illustrate the attribution problem.
He outlines requirements for agent identities, delegated authorityAn agent permission boundary defines and enforces which resources and actions an automated agent is allowed to use., short-lived credentials, federation with legacy systems, policy and audit. Potrec discusses the difficulty of applying these controls consistently across many services and agent types.
Potrec compares SDKs with gateways that keep credentials outside the agent runtime and enforce policy on requests. He also describes gateway limitations, including latency, network bypasses, local execution and operational complexity, before introducing Keycard’s commercial approach.
Watch on YouTube
