The Standard
What AGAP™ is
The Agent Governance and Action Protocol (AGAP™) is an open standard that defines the runtime governance requirements for AI agent systems. It specifies how agents must authenticate, how their actions must be authorised, how sensitive data must be protected, and how every decision must be recorded.
AGAP™ was created by MTE Software Ltd and published under CC BY 4.0. The full specification, including requirement definitions and conformance criteria, is available at agap-protocol.org.
Conformance is structured in three tiers (Core, Extended, and Full), allowing organisations to adopt governance incrementally and verify each level independently.
Why it matters
An open standard with a controlled conformance signal
Open Standard, Not Vendor Lock-In
AGAP™ is published under CC BY 4.0. Anyone can build a conformant implementation, evaluate existing tooling, or contribute to the specification. Choosing Vortalis means choosing an open ecosystem, not a closed one.
Controlled Conformance Signal
AGAP Protocol® and AGAP CONFORMANT® are UK-registered trade marks held by MTE Software Limited (UK00004357019 and UK00004357025, registered 15 June 2026). Implementation is unrestricted; the conformance signal is controlled.
Regulatory Compliance by Architecture
AGAP™ conformance maps to specific EU AI Act articles (Articles 10, 11, 14, 15, 27, 43, 49, and 50), DORA, and NIST AI RMF. Compliance evidence is produced from the same governance the standard requires, not assembled by hand afterwards.
Conformance
Conformance per control is published
Conformance per control is published, with the difference between letter-code-bound and capability-bound rows on the page rather than buried in the test suite.
Every requirement is recorded in one of three categories. A requirement is letter-code-bound when a named test file under tests/conformance/ binds it, so a regulator can read the requirement, the assertion, and the implementation the assertion exercises together. It is capability-bound when the implementation exists and is exercised by the broader test suite but no dedicated letter-coded test has been bound yet. The remainder is not represented, where neither a binding nor a clear implementation pointer exists today. The binding programme is in progress, and capability-bound rows convert to letter-code-bound as named test files land.
A capability-bound row is not marketed as if it were letter-code-bound. The categorisation lives in public so the difference is on the page rather than buried in the test suite. Every Vortalis release is exercised against the AGAP™ Conformance Test Suite in CI, alongside 1000+ platform-wide tests.
Per-tier conformance breakdown
AGAP™ Core
18 controls- 18 of 18 letter-code-bound
- 0 of 18 capability-bound
Foundational governance controls: policy enforcement, credential isolation, audit logging, kill switches, and role-based access.
AGAP™ Extended
11 controls- 11 of 11 letter-code-bound
- 0 of 11 capability-bound
Advanced capabilities: anomaly detection, human-in-the-loop approval, inter-agent governance, runtime resource limits, and workflow enforcement.
AGAP™ Full
7 controls- 1 of 7 letter-code-bound
- 0 of 7 capability-bound
Ecosystem features: governance spine with principal chain tracking, federated governance, cross-tenant policy negotiation, and regulatory export automation. F-09, F-10, and F-12 test files exist in the suite but exceed the public F-01..F-07 numbering range named in AGAP™ Working Draft 04.
Today the totals are 18 of 18 Core letter-code-bound, 11 of 11 Extended letter-code-bound, and 1 of 7 Full letter-code-bound. The Core and Extended bands are now fully letter-code-bound; the remaining Full-band controls are blocked on AGAP™ working-group reconciliation of the underlying requirement statements, not on engineering. The suite also contains test files for F-09, F-10, and F-12, which exceed the public F-01..F-07 range in AGAP™ Working Draft 04; the AGAP™ working group is the right venue to decide whether to extend the public Full range, reclassify those bindings into Extended, or park them under a profile extension. The full per-control mapping is published at docs/agap/conformance-status.md.
Governance you can verify
Vortalis is built on an open standard with published conformance results. No black boxes. No trust-us claims.