Skip to main content
Dutch Ministry of Justice pilots mintBlue for fraud signal exchangeRead the story

AI agents that keep to their mandate.

Give an AI agent a mandate a person signed. The other side checks it before an action counts, and every action and refusal is kept in the audit trail.

AI agents that keep to their mandate.

How it works

How an agent's mandate is checked

Four steps, from the person who signs the mandate to the auditor who checks what the agent did.

Book a briefing
  • 01

    A person signs the mandate

    Someone entitled to act for the company signs what the agent may do: which actions, with which counterparties, up to what amount and until when.

  • 02

    The agent acts with its mandate attached

    When the agent places an order or files a request, the signed mandate travels with it, together with the chain back to the person who gave it.

  • 03

    The other side checks before it accepts

    The receiving organisation checks the signatures, the limit and whether the mandate is still valid, and refuses a request outside it, whatever a console setting says.

  • 04

    Everything lands in the audit trail

    Admitted actions and refusals are both recorded, so an auditor can see afterwards what the agent did and on whose authority.

Where agent permissions usually stop

Most agents run on service accounts and API keys, and their rights sit in the settings of the organisation that runs them. That can be enough inside your own organisation, but when an agent orders from a supplier or files something with a government body, the other side has to take your settings on trust.

A mandate the other side can check itself removes that dependency.

Permissions in settings

  • Rights sit in a console that an admin can change
  • The other side has to trust your identity provider
  • Logs show afterwards what happened but do not stop it
  • Revoking access means updating every system separately

A signed mandate

  • Authority comes from a signature by someone entitled to give it
  • The receiving organisation checks the chain itself before it accepts
  • A limit raised without a signature does not count, so the request is refused
  • Revoke once and every receiver refuses the next request
mintBlue platform illustration

Next step

Start with one agent.

Tell us which agent should act for your organisation, towards whom and up to what limit. We work out the mandate with you and show what the other side checks.