Agent identity, authority and verification
Authority you can verify.
Your AI agents are acting on borrowed human logins and shared, over-privileged keys — so an action often traces no further than a service account. Mandavo issues each agent a distinct, short-lived identity bound to a named human sponsor, enforces it at the moment of execution, and lets any counterparty verify that authority in real time.
- 27%of leaders believe their identity systems can govern non-human identities
- 28%can trace an agent's actions to a human sponsor
- 70%of secrets leaked in 2022 remained valid in 2025
Watch the film
The market we sit inside
An identity layer for the agent workforce.
One credential, four working layers.
Each agent gets a distinct cryptographic identity in a canonical directory, with short-lived credentials scoped to a named human sponsor and policy evaluated at the moment of execution. Every decision is written to an immutable log, replacing borrowed logins and shared static keys.
How it works
Issuance, execution, verification, revocation.
Provision a scoped identity
An administrator, or an AI colleague drafting the change, requests an identity for a new agent. Low-risk grants are issued automatically with full logging; elevated scopes route to a named human sponsor for approval. The agent receives a short-lived credential bound to that sponsor and to the systems it may reach.
Authorize at execution
When an agent attempts an action, Mandavo evaluates policy against the credential's scope, value and transaction thresholds and expiry in real time, then permits, escalates, or denies. The decision and its context are written to the immutable log.
Verify a counterparty's agent
Before committing to an interaction, a vendor, bank or another company's agent calls the verification API to confirm the presenting agent's credential is valid, in-scope and not revoked, and to see the accountable legal entity and human sponsor. If authority has been revoked, the check fails immediately.
Revoke authority
A sponsor or AI colleague revokes an agent's authority when it is compromised or its task is complete, and the revocation propagates across the registry so counterparties cannot rely on stale credentials. The action is recorded for audit.
Why this position holds
Root of trust and neutral verification surface, held together.
An internal permission is not something a counterparty can accept. Mandavo keeps control and proof separate, then joins them in one credential.
- W3C Verifiable Credentials
- SOC 2 / ISO 27001 evidence mapping
- DIFC enforcement forum
A named human on every action
Each credential binds an agent to the accountable human fiduciary who granted it. Attribution stops at a person, not a shared service account — a defensible chain of accountability for every autonomous action.
Least privilege, bounded blast radius
Short-lived, scoped credentials replace static, broadly-privileged keys. A leaked credential is limited by scope, value threshold and expiry, so a single compromise cannot defeat large parts of your security investment.
Portable proof on open standards
Credentials are issued as W3C Verifiable Credentials and Decentralized Identifiers rather than a proprietary token format, so they remain interoperable and independently verifiable across organisational boundaries.
A neutral registry incumbents cannot occupy
A vendor whose customers are each other's counterparties cannot also be the neutral registry between them. Mandavo is a picks-and-shovels authority layer, largely independent of which agent vendors ultimately win.
Questions before you deploy
What a security and identity team should ask.
What does Mandavo replace inside our tenant?
Agents borrowing human logins and sharing static, over-privileged keys. In their place, each agent receives a distinct cryptographic identity, short-lived credentials scoped to a named human sponsor, and authorization evaluated at the moment of execution — with every decision written to an immutable log.
How does a counterparty verify one of our agents?
The same credential is reissued as a W3C Verifiable Credential binding the agent to a legal entity, authority scope, value and transaction thresholds, an expiry, and the named human fiduciary. A real-time verification API lets a vendor, bank or another company's agent check validity, scope and revocation status before committing to an interaction.
What is available today, and what comes later?
The current scope is the Control layer — distinct per-agent identities, short-lived sponsor-scoped credentials, execution-time authorization, and an immutable audit log — the capability CISOs are budgeting for now, with FTLAB portfolio ventures as first design partners. Attestation and Verification are scoped initially as issuance of the same credential as a W3C Verifiable Credential and a validity/revocation check between known parties.
How does this support our compliance evidence?
Credentials are short-lived, least-privilege and revocable by design, and every issuance and authorization decision is written to an immutable log to support SOC 2 / ISO 27001 service-account and key-management evidence. The governance console produces a current view of active agents, their scopes, sponsors and revocation events without manual reconciliation.
What does Mandavo deliberately not do?
The verification registry exposes only what a counterparty needs to make a trust decision — validity, scope, and revocation status — not the broader contents of your tenant. Mandavo is an identity and authority layer, not an agent platform, and it does not decide which agent vendors you run. Whether cross-counterparty verification becomes load-bearing across the wider market is not something we assert; the Control layer stands on its own inside a single organisation regardless.
Who is accountable, and where is that enforceable?
Every credential names a human sponsor who holds fiduciary accountability for the agent's authority. High-risk grants, elevated scopes, and production-affecting policy changes pass through explicit approval gates; AI colleagues do the operational work but cannot self-approve elevated authority. DIFC provides the legal forum in which the sponsor binding is enforceable.
Give every agent a name, a scope, and an expiry.
Tell us about your agent fleet and where attribution currently stops. We will walk through issuance, execution-time enforcement, and verification against your stack.