Bring the agents you have. Give each one limits and a record.
Enrol an existing agent without a rewrite. It gets credentials, an access policy, a governed path to tools and other agents, and a place in the record. Start with one agent, in your environment.
Your agent gets limits and a record. Its code does not change.
Your team keeps building the agent the way it does now. Ares adds what the agent may do for each job, and writes down what it did.
- It signs in as itself, through your identity provider (agent authentication).
- It gets a credential for this job only. The credential expires.
- An access policy is checked on every call it makes.
- It reaches tools and other agents through one controlled path.
- Every call it makes is recorded, allowed or refused.
What we need from you
- One agent your team already runs.
- One tool it calls.
- A test directory, so no real user is involved.
What happens
- The agent is enrolled.
- An access policy is set with your team.
- The agent runs its normal job.
- One step is refused on purpose, so you see the refusal and its reason.
What you keep
- Your own evidence that it works in your environment.
- The record of the run.
- The verifier result, from a check you run on your own machine.
Your directory, your protocols, your models, your hardware.
The evaluation names your systems and what each one needs. Products are named here only where the integration is built.
- Identity provider: Entra ID today. Other directories on request.
- Protocols: agents connect over A2A, MCP or our SDK.
- Models: your choice, local models included.
- Deployment: Azure SaaS, hybrid, or any Kubernetes in your building.
For your security review
Your reviewer will ask where data goes, what an agent can act as, and what is recorded. Security and data handling answers those questions in plain text. The architecture and security brief goes deeper, on request.
The record of your evaluation is yours. Export it and check it with the open verifier, offline, on a machine that is not ours. If a record was changed, the check fails.
What your developers can read and run today.
Documentation
The concepts, the guarantees, the sandbox scenarios and what ships next.
Read the documentationSandbox
Real agents on demo data. A step allowed, a step sent to a person, a step refused, and the record.
Open the sandboxOpen source
The verifier that checks a record offline, and the repositories that follow it.
See the repositoriesBuying
Licence or subscription. Buy direct, or through Azure Marketplace on your Azure account. Private offers are available on the same listing. See pricing.
What the evaluation does not show
- It covers one agent and the tools it calls, not every agent you run.
- It does not test whether your model gives correct answers.
- It does not find agents you have not enrolled.
What platform teams ask.
Evaluate Ares with one of your agents.
Bring one agent and one tool it calls. You keep the evidence from the evaluation.
A senior member of the team replies within two business days.