Tyche InstituteEUDI verifier bench · research demo

The agent that cannot overspend

Can you hand an AI assistant your bank card — and be sure it can’t overspend or be tricked?
Buttons — coloured & raised: click these Panels — flat & bordered: they show what’s happening dotted term — click any dotted word for a plain-language explanation
Your phone · the walletreal device ✓
EU Digital Identity Wallet
The verifier · four gates every payment must passthe bouncer’s checklist
1○
Is it really your assistant asking?
its signed credential is checked — not just a password
2○
Is the assistant’s computer genuine & un-tampered?
the server the assistant runs on — not your phone — proves its software via hardware attestation
3○
Did a trusted authority vouch for it?
the credential’s issuer must be on an official national trusted list
4○
Is this exact payment what you allowed?
three checks against your permission slip:
·payment type is on your allowed list
·amount is within your limit
·the tamper-seal still matches
The permission slip & the decision
SIGNED BY YOU
Permission slip · MachineMandate
assistant maypay invoices → acme-corp
spending limit€500 per payment
tamper-seal of the approved payment700340c5…
Press “How it’s set up”, then try the scenarios ↓
▸ technical detail
Start here
▸ Under the hood — the real benchconsole · standards · run it live
run a scenario above, replay the genuine recording, or trigger a real live run.

Open standards in play — hover any chip

Provenance

Real EC reference verifier · real national trusted lists · a real EU wallet tap on a physical phone. Attestation appraised by Veraison (IETF RATS); transparency cross-verified with SCITT/AAC. swtpm — emulated attestation, not hardware-rooted. Reproduce: git clone → docker compose up → python src/run_bench.py · prefer the previous engineering view? instrument reel →