Identity proves who an agent is. Payment infrastructure lets it transact. Neither decides what it is authorised to do.
Card networks, commerce protocols, agent identity standards and stablecoin rails are being built quickly and well. They answer who is calling, what instrument it holds, and how value moves. None of them answers whether this particular payment is within the authority a person actually granted — because that depends on the budget already spent, this counterparty's history, and whether a human would have wanted to be asked.
That is the layer mnd8t is built for. We also maintain a public reference on the whole stack — the Agentic Authority Stack, a dated tracker, and analyses of AP2, ACP, Visa TAP and Mastercard Agent Pay.
Read the intelligence hubFour steps between an agent and your money.
Write the mandate
Approved counterparties, per-transaction limits, daily and monthly budgets, permitted purposes, operating hours. Versioned and immutable once published.
Run it in shadow
Replay real transactions and see what mnd8t would have decided. Zero risk to the workflow you already have. Switch to enforcement when the policy has earned it.
The agent asks before it pays
A deterministic engine answers APPROVE, REJECT, or ESCALATE in seconds, with the full reason set and a rule-by-rule trace.
You execute, mnd8t proves
An approved action receives a one-time signed authorisation artifact your own system verifies, claims, and executes with credentials mnd8t never touches.
An approved payment is not a fulfilled mandate.
mnd8t doesn't stop at permission. It creates a traceable link between what an agent was authorised to do, what it actually did, and the evidence that the intended outcome occurred.
An agent authorised to buy 100 units for no more than £10,000 can pay £9,700, on time, to the right supplier, entirely within its mandate — and take delivery of 80. Every authority system stops one step before that fact. A mandate that records only what was permitted cannot tell you whether delegating it worked.
Every decision is a document you can verify without us.
Who delegated the authority, which policy version applied, why the decision was made, who approved any exception, and what actually executed — Ed25519-signed and hash-chained. Change one timestamp and verification fails.
Start in shadow. Enforce when it's earned.
A sandbox key, an agent, and a mandate. Most teams reach their first decision in under 30 minutes.
Get a sandbox key