About AGF
An open standard for authorizing AI agents.
Autonomous AI agents call APIs, delegate authority, and act without a human approving each step — yet no shared model existed for what they are allowed to do. The Agent Governance Foundation develops the Agent Authorization Protocol (AAP) in the open to provide one.
AGF is an open standards initiative maintained by INTREXA TECHNOLOGIES (OPC) PRIVATE LIMITED — not a separately incorporated foundation. Looking for a commercial implementation? Visit INTREXA AXIS →
Apache 2.0
Specification license
Working drafts
Status of every spec
Public
Developed on GitHub
Why this exists
The gap we're closing
Agents are already in production. They're reading and writing files, calling APIs, sending emails, managing cloud infrastructure — most of them running with whatever API key was in the environment at startup, logging nothing useful, with no revocation mechanism beyond "kill the process."
This is how the web looked before session management was standardized. Every team improvising, every implementation slightly different, every system insecure in its own way. IAM addressed this for human identities and DevOps practice for machine identities. Autonomous agents still lack a shared answer.
The window to establish shared standards is while the ecosystem is still forming. Once every agent framework has built its own identity model and delegation mechanism, interoperability becomes a much harder problem. We aim to do for agent authorization what OAuth did for delegated authorization: a common substrate that everyone builds on, so the hard security work gets done once and done well.
What we publish
One standard, many implementations.
The open standard
- AAP-Core: the normative kernel
- Delegation tokens and chains
- Revocation and branch cut
- Policy model and versioning
- Audit trail and decision provenance
- Execution-time authorization validation
- Agent Identity, Trust, and Lifecycle frameworks
- Governance glossary
Implementations
Anyone can implement AAP. INTREXA AXIS is a commercial implementation built and operated by INTREXA. It is one implementation of the standard, not the standard itself.
Visit INTREXA AXIS →Design constraints
Our principles
These aren't values-statement placeholders. They're the design constraints that drive every architectural decision in the specs.
01
Resource owner decides
The entity that owns or operates a resource has final say over what agents may access it, regardless of what any agent claims about its own authority. Governance cannot be delegated away from the owner.
02
Trust is evaluated separately from policy
Whether a request is policy-compliant and whether the agent making it is trustworthy are two different questions. Conflating them leads to systems where a technically-authorized-but-compromised agent sails through.
03
Decisions must be auditable
Every authorization decision should be signed, structured, and replayable. Not for compliance theater — but because you cannot debug, improve, or contest a system whose decisions leave no trace.
04
Expiration by default
Permissions should decay unless explicitly renewed. Long-lived credentials are a liability, not a feature. Short-lived grants with renewal obligations create natural checkpoints for re-evaluation.
Help shape the standard.
Read the specifications, propose a change, or report a gap. The work happens in public, and contributions are welcome.

