Identi3

AI agents are quickly moving from experimentation to real-world deployment, but one critical question remains: how do you establish trust when agents start acting on behalf of users?
In a recent webinar, Mike Parkhill (Head of Engineering at Dock Labs) and Agne Caunt (Product Owner at Dock Labs) explored this challenge and demonstrated how identity infrastructure can play a central role in solving it.
The session focused on Truvera’s MCP (Model Context Protocol) server, showing how agents can issue, verify, and eventually hold digital ID credentials, and how this enables more secure, auditable, and constrained agent behavior. Along the way, they walked through a live demo of credential issuance and verification, and shared their perspective on where agent identity, delegation, and agentic commerce are heading next.
(01:08) Why agent identity is becoming a problem
(02:20) What MCP (Model Context Protocol) is
(03:19) Goal: identity infrastructure for AI agents
(04:27) What MCP enables for agents (analogy + capabilities)
(05:56) Demo setup (Claude + web wallet)
(14:27) Roadmap: wallet MCP and agent capabilities
(15:16) Agent-to-agent (A2A) and DIDComm direction
(16:13) Introduction to Agentic Payment Protocol (AP2)
(18:02) AP2 mandates (cart, intent, payment) explained
(19:51) Demo: issuing a cart mandate to an agent wallet
(21:31) End of demo and transition to Q&A
(22:21) What is an agent’s identity?
(25:05) How MCP improves security and limits agent scope
(28:07) Schema flexibility and support for new protocols
(30:03) Ease of implementation and setup
(31:43) How agents get their identity (onboarding)
(33:04) Human-to-agent delegation model
(34:19) EUDI and business wallet discussion
(40:38) What happens when an agent invokes MCP tools
(42:52) Multi-tenant vs one-to-one MCP architecture
(45:36) Why did:cheqd was chosen
(47:41) Real-world use cases (e-commerce, travel)
(49:01) Sensitive use cases (loans, insurance, documents)
(50:23) DID methods (did:key vs cheqd) explained
(52:45) Closing remarks and next steps

📚 EXPLORE:
Website - https://www.dock.io/
👨‍👩‍👧‍👧 FOLLOW:
LinkedIn - https://www.linkedin.com/company/docknetwork/

Identity fragmentation isn’t usually the result of bad architecture. It’s the natural byproduct of growth. New apps get added. Business units operate independently. Acquisitions bring in new identity stacks. And over time, even well-designed IAM environments start to sprawl.
In our recent masterclass, Richard Esplin (Head of Product) and Agne Caunt (Product Owner) walked through what this looks like in the real world and, more importantly, how organizations can evolve toward a unified identity architecture without ripping out the systems they already rely on. The session explored the limits of traditional federation, the shift toward reusable digital ID credentials, and a practical, phased path teams can use to reduce duplication, improve flexibility, and move closer to a zero trust model.
(00:00) — Welcome and webinar overview
(00:57) — Why identity architectures keep fragmenting
(01:28) — The real-world IAM problem 
(02:52) — Example: a scaled consumer business with identity silos
(04:27) — Typical federation-based IAM architecture
(06:01) — Why federation breaks down in practice
(08:52) — What IAM architects are reporting in the field
(13:09) — The mindset shift: from system integration to identity ecosystems
(17:07) — The generic reusable credential architecture
(18:22) — Wallet integration overview
(18:44) — Flow 1: Onboarding and credential issuance
(20:53) — Flow 2: User-initiated verification from an app
(22:01) — Flow 3: User-initiated verification from a relying party
(23:05) — Flow 4: Call center / relying-party initiated flow
(24:21) — How to evolve a fragmented architecture (phased approach)
(25:41) — Phase 1: Start with one painful use case
(26:02) — Phase 2: Use the IdP as a credential verifier bridge
(28:00) — Phase 3: Direct verifier integrations
(28:36) — Phase 4: Reducing reliance on the IdP
(30:12) — Practical implementation tips
(34:03) — Trade-offs and considerations
(36:06) — Key advantages of the credential model
(37:46) — Q&A begins

📚 EXPLORE:
Website - https://www.dock.io/

👨‍👩‍👧‍👧 FOLLOW: 
LinkedIn - https://www.linkedin.com/company/docknetwork/

AI agents are rapidly changing the shape of the internet. What started as an effort to keep bots out is quickly becoming a much more complex challenge: distinguishing humans from machines, enabling safe automation, and doing all of it without forcing users to overshare their identity.
Against this backdrop, “proof of human” is moving from a niche concept to a foundational requirement for many digital experiences.
To unpack what’s really happening, and what the identity ecosystem needs to do next, we hosted a conversation with Ajay Patel, Head of World ID at Tools for Humanity, and Kim Hamilton Duffy, CEO of a stealth startup and former Executive Director of the Decentralized Identity Foundation.
The discussion explored the rising pressure created by AI-driven abuse, the risks of over-identification, the role biometrics can play when implemented carefully, and why interoperable, narrowly scoped credentials may be the path forward.
(00:00) — Introduction and session overview
(02:57) — Ajay Patel introduces World ID
(09:51) — Urgency of proof of human in the AI era
(10:50) — Why traditional bot defenses are failing
(12:38) — Risks of over-identification and data oversharing
(14:41) — Are we overreacting to the AI/bot problem?
(17:52) — Gaps in current digital identity infrastructure
(21:53) — Privacy by design vs. surveillance risks
(24:48) — Design principles for future identity systems
(31:21) — World ID Orb and biometric approach explained
(37:34) — Role and concerns around biometrics
(41:00) — Centralization risks and self-custody principles
(44:20) — Hardware trust and decentralization challenges
(48:06) — Interoperability with verifiable credentials and mDLs
(53:02) — Why composability and standards matter
(55:34) — Q&A: biometric changes and credential refresh
📚 EXPLORE:
Website - https://www.dock.io/
👨‍👩‍👧‍👧 FOLLOW:
LinkedIn - https://www.linkedin.com/company/docknetwork/

As Europe moves closer to rolling out the European Digital Identity Wallet, questions are shifting from if to how, and what this really means for banking, payments, and trust online. In a recent live webinar, we explored these questions with Marie Austenaa, Payment Domain Lead for the EUDI Large Scale Pilots and Head of Digital Identity at Visa. Drawing on her experience across EU policy, large-scale pilots, and global payment networks, Marie offered a grounded, practitioner’s view on where the EUDI wallet creates real value for banks and payment providers, and where the hard work still lies.
(00:00) – Introduction
(03:56) – Why the EUDI Wallet is a “present on a silver plate” for banks
(12:59) – Wallets as a potential payment method
(15:49) – Limits of document verification and the need for cryptography
(18:14) – Expected impact on fraud prevention
(21:01) – Beyond banking: age verification and eligibility proofs
(24:44) – Privacy concerns and “Big Brother” fears
(28:42) – EUDI timelines and why they’re aggressive
(32:59) – What banks must do to prepare
(36:13) – Lessons from global payment networks
(41:14) – AI agents and agentic commerce enter the picture
(45:43) – Should AI agents have their own identities?
(47:22) – How payment networks are approaching agentic commerce
(50:17) – Audience Q&A begins
📚 EXPLORE:
Website - https://www.dock.io/
👨‍👩‍👧‍👧 FOLLOW:
LinkedIn - https://www.linkedin.com/company/docknetwork/

To explore what a better model could look like, Dock Labs hosted a live webinar on the future of caller authentication, presenting a joint proof of concept developed with GSMA Telefónica Tech and TMT ID. The session demonstrated how callers can authenticate themselves in seconds using a secure digital identity wallet, without sharing sensitive personal data and without relying on knowledge-based authentication or one-time passwords.
The discussion examined the growing fraud landscape, the role of mobile operators as a new root of trust through SIM-based identity, and how decentralized identity and verifiable credentials can transform call center security while improving customer experience and privacy.
The session featured Glyn Povah, Global Head of Product Development at Telefónica Tech, and Hélène Vigue, Identity and Data Director at GSMA, who shared insights from the pilot and outlined how the mobile industry is working together to restore trust in voice communications.
(0:00) — Introduction
(1:00) — The problem with today’s call center authentication
(5:00) — Strategic context: rising fraud and erosion of trust in voice and messaging
(8:44) — Call center impact: millions of callers spending minutes just to authenticate
(9:20) — The three goals of the proof of concept: faster, stronger, more private authentication
(10:16) — Global fraud landscape: $1 trillion in losses and rising impersonation scams
(13:38) — Why the voice channel needs next-generation authentication
(14:50) — Live demo begins: caller navigates IVR
(16:21) — Why the demo is a major UX improvement over KBA and SMS OTP
(17:13) — How the mobile operator issues the identity credential to the wallet
(18:09) — Decentralized identity explained
(22:26) — Why the flow feels familiar (similar to open banking approvals)
(23:08) — Open standards: DIDComm, encrypted messaging, verifiable credentials
(24:47) — Success metrics for the pilot explained25:13 — Integrating telco APIs, decentralized identity, and a call center platform
(26:28) — Business KPIs: handle time, fraud reduction, customer experience
(27:46) — Early user feedback and privacy benefits
(30:08) — Observations from real call center operations
(31:22) — Cost per minute of call center time and ROI opportunity
(32:00) — Why the technology integration was easier than expected
(34:40) — How this model reduces impersonation fraud
(36:04) — SIM card as a new root of trust for identity
(39:38) — How carrier network APIs secure credential issuance
(44:40) — GSMA’s role in scaling industry-wide solutions
(47:37) — Audience Q&A begins
📚 EXPLORE:
Website - https://www.dock.io/
👨‍👩‍👧‍👧 FOLLOW:
LinkedIn - https://www.linkedin.com/company/docknetwork/