Agent Identity & Security
Why can't I just use a static API key for my agent in a development environment?
Static API keys in development create a security gap because they often leak into code, config files, or logs, and may be accidentally promoted to production. They also prevent you from testing authentication and authorization logic early. Catalyst lets you use workload identities in development too—identities are scoped to a development environment and short-lived, so you can validate agent security before deployment. This catches misconfigurations early without risking production keys.
Was this article helpful?
Your feedback helps improve Diagrid's FAQ experience.
Keep reading
More Diagrid FAQ articles
- Agent Identity & Security
What is a workload identity for an AI agent and why can't I just use a shared API key?
Explains workload identity for AI agents and the security limits of shared API keys in production.
- Agent Identity & Security
How does Catalyst assign a workload identity to an agent runner like LangGraph or CrewAI?
Describes how Catalyst injects workload identities into framework-agnostic agent runners.
- Agent Identity & Security
What security problems do shared API keys cause when multiple agents run in production?
Lists security problems from shared API keys in multi-agent production environments.