iDen2
AI agents

An agent is only as trustworthy as the principal behind it.

Bind every autonomous action to a verified person or organization. Define scope, expiry, and revocation cryptographically. Any counterparty can verify live.

See the platform
Industry problem

Agents transact today with shared secrets and hope.

The API key is the identity. Scope lives in documentation. Revocation is asynchronous. When something goes wrong, no one can prove who authorized what.

  • OpenAI, Anthropic, and enterprise agent stacks all rely on bearer tokens.
  • Agent-driven fraud is projected to be the top financial crime vector by 2028.
  • Regulators are converging on requirements for named accountability of AI actions.
Our perspective
“As AI agents start acting on our behalf, we need to know they're really working for us, not just once, but every step of the way. We can change our minds or take back permission at any moment, and our agents should always be able to show they're still acting for us.”
Philip Fahim
Philip Fahim
Co-Founder & Chief Product Officer
iDen2 solution

Signed mandates. Continuous proof of control. Live revocation.

Every agent presents a signed mandate from a verified principal at the moment of transaction. Continuous Agentic Proof of Control (CAPoC) re-attests every few seconds. Any counterparty verifies, any principal revokes.

  • Signed, scoped, expiring mandates in W3C VC format.
  • CAPoC, live re-attestation of principal control.
  • Instant revocation propagated to every counterparty.
  • Signed audit trail per action, per agent, per principal.
Platform capabilities

An AI agent needs three things: ID, context, and delegation.

ID bound. Context set. Authority delegated.

A verified human binds credentials from trusted sources in their wallet, then delegates scoped authority and context so an agent can reach resources on their behalf.

Government
Bank
Employer
WalletID bound to trusted sources
Alex Larsen · mandate
Agent Delegation
Verified
Subject
Booking Agent · v1.4
Scope
Travel · EMEA
Spend
••••••
Expiry
72 hours
Status
Revocable
Signed · SD-JWT VCdid:web:iden2
Alex Larsen · session
Agent Context
Verified
Subject
Booking Agent · v1.4
Policy
Corp travel v3
Preferences
Economy+
Allowlist
Airlines · hotels
CAPoC
Every 45s
Signed · SD-JWT VCdid:web:iden2
AI Agentpresents mandate + context
  • API
  • Data
  • Tools
  • Payments
Real use cases

How signed agent mandates are used.

Booking agents
Travel and procurement agents transact under corporate mandates.
Treasury agents
Payment execution stays inside signed spend limits and allowlists.
Data agents
Autonomous access to systems is bound to a named employee.
Customer support agents
Support bots act only within a scoped, revocable customer mandate.
DevOps agents
Infrastructure changes require a signed principal and an expiry.
Research agents
Model runners present authority before pulling sensitive datasets.
Marketplace agents
Shopping agents prove who they spend for at checkout.
Compliance monitors
Watchdogs verify every agent action against the live mandate.
Cross-org agents
A partner agent presents a signed, limited delegation before it can call your API.
Outcomes

Measurable results in weeks, not quarters.

0
shared API keys
45s
CAPoC cadence
100%
actions attributable
MCP
compatible
Next

Bring iDen2 to your ai agents stack.

See a live workflow tailored to your systems, or explore the developer sandbox.

Developer docsAll applications →