Glossary

Scoped credential

A scoped credential covers a named set of actions for a limited time, instead of everything an account can do. When the job ends or the time runs out, it stops working.

In a run

The credential is the second line of every run. In the supplier follow-up run it names five actions: read open orders, email the supplier on file, read supplier replies, change a delivery date with buyer approval, and update the expected invoice date. It expires with the job.

Our word for it

Credentials for agents: one credential, one job.

What a scope names

A scope names actions, not only systems. "Email the supplier on file" is narrower than "use the mailbox": a send to a new address falls outside it. A step that needs a person can sit in the scope itself, as the delivery date change does above.

A credential as a mandate

A scope can hold more than a list of actions. In the agent mandate run, the purchasing agent’s credential is a mandate: a ceiling, a list of approved merchants and an expiry. A merchant off the list is refused. A bundle above the ceiling is refused. The purchase inside the mandate goes through, and the mandate closes when it expires.

No long-lived secrets

Agents do not need long-lived secrets to reach the services behind Ares. The credential for the job is what lets them through. When the job ends, no standing access is left behind.

Where it stops

  • A scope is as narrow as the rules you approve.
  • Exporting a credential in open credential formats is planned.

The sandbox shows the credential for each scenario before the first step runs.

Related terms

  • Agent authenticationAgent authentication is how a system knows which AI agent is calling it.
  • Least privilegeLeast privilege means an account holds only the access it needs for its task, and nothing more.

Tell us about one workflow.

We will say whether an agent should do it, and what the first step costs.

A senior member of the team replies within two business days.