No limits
A key or a saved card lets an agent do anything the account can do. Nothing says how much it may spend, with whom, or until when.
Open source · TypeScript · Apache 2.0
v0.3 · ALPHA
Mandates, not full powers.
Plenipo lets AI agents act for you only within limits you approved in your EUDI Wallet, and lets any service verify that mandate before the agent acts.
Plenipo is in alpha. Access is by invitation for developers, banks, wallet providers and agent platforms. Not for production use with real money or data yet.
Request an inviteAI agents are getting full powers
AI agents are starting to book, buy and pay on our behalf. Today the only way to let them act is to hand over passwords, API keys or card details: full powers, with no limits and no expiry.
No accountable person
Agent registries can tell which software acted, not who is behind it and with what authority. Services cannot tell an authorized agent from a hijacked one or a prompt injection.
Hard to stop
Revoking a password or a card breaks everything else that depends on it. There is no clean way to withdraw one agent's permission.
Plenipo replaces full powers with a mandate: approved by a verified person in their EUDI Wallet, limited in scope, spending and time, checked by the service before every action, and revocable at any time.
How verifiable agent mandates work
- 01
Approve a mandate in your wallet
Your EUDI Wallet presents your PID, bound to the mandate through OpenID4VP transaction data.
- 02
Your agent acts within scope, limits and expiry
Allowed actions and counterparties, spending limits, an expiry. Sub-delegation can only narrow it.
- 03
Any service verifies before it executes
Through an MCP integration for AI tools or an HTTP gateway for APIs. You can revoke anytime.
The root of every chain is your PID presentation: no new identity, no new root key.
Built on open standards
- eIDAS 2 / EUDI Wallet
- OpenID4VP 1.0
- SD-JWT VC
- IETF Token Status List
- Model Context Protocol
- EUDI e-mandate · TS12
Roadmap
Plenipo targets aligned to the eIDAS 2 regulatory calendar.
Now · Alpha (v0.3)
Invite-only. Working library and full sandbox (simulated bank, wallet and agent platform). Two independent security reviews completed. Not yet tested with a production wallet.
December 2026 · Public beta (target)
EU Member States must make the EUDI Wallet available to citizens.
Plenipo goal: first end-to-end tests with real wallets, public sandbox, open repository.
December 2027 · Production-ready 1.0 (target)
Banks, payment institutions and other regulated relying parties must accept the EUDI Wallet.
Plenipo goal: a stable 1.0 for services that need to verify agent mandates.
Dates refer to Regulation (EU) 2024/1183 (eIDAS 2). Plenipo milestones are targets, not commitments.
Open source, Apache 2.0
Plenipo is open source under Apache 2.0. During the alpha the repository is shared with invited partners; it will be public under the plenipo-net organization on GitHub.
Plenipo is currently developed by Fabio Lalli, who works on AI adoption and strategy and is a partner in LocalAI, the open source project for local, private AI with real sovereignty.
EUDI Wallet and AI agent mandates: FAQ
What is Plenipo?
Plenipo is an open source TypeScript library that lets a person authorize an AI agent with a mandate approved from their EU Digital Identity (EUDI) Wallet, and lets any service verify that mandate before the agent acts.
What problem does Plenipo solve?
Today AI agents act with passwords, API keys or card details, which give full powers with no limits, no expiry and no proof of who authorized them. Plenipo lets a verified person grant an agent a limited, revocable mandate from their EUDI Wallet, and lets services check it before the agent acts.
What is a mandate?
A mandate is a signed authorization with a scope (allowed actions and counterparties), spending limits and an expiry. The person can revoke it at any time, and any sub-delegation to another agent can only narrow it.
How is this different from giving an agent an API key or a password?
A key gives full powers and says nothing about who is behind the agent. A Plenipo mandate is tied to a verified person through their wallet, is limited, expires, and is checked by the service on every action.
Which standards does it use?
Plenipo uses eIDAS 2 and the EUDI Wallet, OpenID4VP 1.0 transaction data, SD-JWT VC, IETF Token Status List for revocation, and the Model Context Protocol for AI tools. It also supports the EUDI e-mandate type from technical specification TS12.
Is Plenipo ready for production?
No. Plenipo is an alpha (v0.3) available by invitation. The cryptography is real, but it has not yet been tested with a production wallet on a device.
When will it be available?
The Plenipo target is a public beta around December 2026, when EU Member States must offer the EUDI Wallet, and a production-ready 1.0 ahead of December 2027, when banks and other regulated services must accept it.
Is it open source?
Yes. Plenipo is open source under the Apache 2.0 license. The repository will be public under the plenipo-net organization on GitHub.
Who is behind Plenipo?
Plenipo is currently a project by Fabio Lalli, who works on AI adoption and strategy. He is a partner in LocalAI, the open source project for running AI locally and privately, for real AI sovereignty. Plenipo is developed in the open and aims to become a community project.
Who is it for?
Plenipo is for developers building AI agents, banks and payment providers, wallet providers and agent platforms that need to know who authorized an agent and within which limits.
Request early access.
We are onboarding a small group of design partners during the alpha.