Where APS fits
| Layer | What it is responsible for |
|---|---|
| Agent framework | Runs the agent and coordinates its work |
| Identity provider | Supplies identities and authentication |
| APS authority records | Describe delegated permissions so that a verifier can check them |
| Enforcement boundary | Checks permission before a request reaches a protected resource |
| Signed evidence | Records the decision so that it can be checked later |
These layers work together. APS does not replace a framework, an identity provider or the security controls of the resource.
The difference in one example
A person authorizes an agent to buy supplies for up to $200. The framework decides how the agent completes the task. APS records the $200 limit in a signed delegation, and a verifier can check it. An enforcement boundary that sits in front of the payment can refuse a $250 request before it is sent.
That protects only the purchase path where the boundary is in place. An agent with another route to the payment system is not checked.
Tests written by other projects
The benchmarks page reports how APS behaves on tests written by other projects. Each report covers specific cases and revisions and is not a certification.