Okmand sits between your AI agents and your business. Before an agent places an order, pays an invoice or signs a contract, the right person approves it on their phone with a legally valid signature. You keep the proof.
An AI agent can prepare a payment in seconds. Who is accountable for it?
No action without a yes
Agents prepare. A named person decides. If nobody approves, nothing happens.
A signature that holds up
Not a click, but a qualified electronic signature, which EU law treats like one made by hand. Your people use the one they already have.
Proof for your auditor
For every action: who approved it, when, and the document showing they were allowed to. It cannot be edited afterwards.
| Approve button | Okmand | |
|---|---|---|
| What it is | A click | A legally valid signature |
| What people sign with | A login to that tool | Your existing qualified signature |
| Who can approve | Anyone with access | Only people you authorised |
| The record | With the vendor, editable | Tamper-proof, and yours |
| When someone leaves | Nobody notices | Their authority stops that day |
Four steps. No new habits.
Bence Kovács may approve
This is the product. Try it.
The real screens, running right here. Open a request and sign it; any six digits work as the PIN.
Orders, payments, contracts, bookings.
You stay in control.
One switch stops everything
Stop one agent or all of them, instantly. Try it.
Limits that hold
Per action and per month. Requests still waiting count too.
No authorisation, no action
If nobody is authorised, the answer is no. A director can sign a one-off exception.
Ready for the EU digital identity wallet
Every EU country is introducing a digital wallet that people can sign with. When your people have one, they sign with it. Your process stays the same.
Connect an agent in five minutes.
One connection. Any agent platform.
The agent asks for approval with a single call and gets back a signed receipt your own systems can verify.
- Claude, ChatGPT, Copilot, Gemini, Grok or any MCP client
- REST and a TypeScript SDK for everything else
- Signed receipts your ERP can verify offline
The standards behind iteIDAS, EU Trusted Lists, SD-JWT, timestamping
Qualified signatures
From any certified provider, including the one you already use. We connect, we do not sign.
Certificates checked
Each certificate is validated against the EU Trusted Lists when signing.
Portable authorisations
The same format the EU wallet uses.
Timestamped record
The state of the record is anchored by an external timestamp.
Instant revocation
A revoked authorisation stops working at the next request.
Platform-neutral
Works with any agent platform. No lock-in.
Check a signature yourselfChange the data and watch the fingerprint break
This is what Bence signed. Change anything and the fingerprint stops matching. Your browser does the calculation, with real SHA-256.
……Start with a pilot. Prices are being set with pilot customers.
Pilot
Start hereOne workflow, a few weeks
- Fixed scope, agreed up front
- For example purchase order approvals
- Set up together with us
Cloud, EU
Subscription per company
- By number of agents and approvers
- Signatures included, usage above that
- EU data centres only
On your servers
Annual licence plus support
- Runs on your infrastructure
- Your keys, your signature provider
- For regulated sectors
What people ask first.
What is a qualified electronic signature?
A digital signature created with a certified provider after your identity has been checked. Under EU law (eIDAS) it has the same legal effect as a handwritten signature in every member state. Many Hungarian companies already use one to sign contracts and filings.
Do we need a new signature for this?
No. If your company already has qualified electronic signatures, your people keep using them, whichever certified provider issued them. Okmand does not issue signatures; it connects to the provider. We connect providers one by one, so if yours is not connected yet, adding it is part of the pilot. If you have none, we help you get one.
Is an approval signed this way legally binding?
The legal effect of the signature comes from EU law. How that applies to your specific authorisations and transactions is something we go through with your counsel during the pilot.
Does every small thing need this kind of signature?
By default, yes. A director can set an amount below which a quick confirmation on the phone is enough. The record always shows that for what it is: not a signature.
What happens when a signer leaves the company?
Authorisations belong to the company, not the person. The leaver's signature is revoked at once and the authorisation pauses until a current representative signs it again.
Does AI decide anything?
No. Fixed, inspectable rules decide who a request goes to. A person always has the final word.
What works today?
The product is in development. The screens and flow you see here are real but run on a test signer. The first certified provider integration and legal review come before the pilot.
Put a signature behind every agent action.
We are running pilots with companies in Hungary. One workflow, a few weeks, real evidence.
- A 30-minute walkthrough on your own workflow
- A scope agreed together, no commitment
- An answer within two working days