Your EUDR due diligence, tracked from your AI assistant
- A screened catalogue: your product codes checked against Annex I of the regulation, so you know what is in scope.
- Tracked lots: status of each delivery, supplier data, plot geolocation and satellite checks.
- Documented risk: country risk, assessment and mitigation actions, tracked through to closure.















See the platform in action
An Orki expert will get in touch to arrange your demo.
Orki uses your data to handle your request and get back to you. You can access, correct or delete it at any time. Privacy policy · Legal notice
Request sent!
We have received your request. Our team will be in touch very shortly.
How did you hear about us?
Something went wrong
Please try again later or email us directly at contact@orki.green.
Which lots are blocked, and what is missing for each one?
3 lots out of 18 are blocked:
| Lot | Commodity | What is missing |
|---|---|---|
| 2026-041 | Cocoa, Côte d'Ivoire | Geolocation of 12 plots |
| 2026-047 | Timber, Brazil | Supplier statement |
| 2026-052 | Coffee, Ethiopia | Risk mitigation |
The other 15 lots are ready. For the cocoa, geolocating the 12 plots is enough to unblock the lot. Would you like the list of the plots concerned?
Fictitious conversation, sample data. The lot status is the EUDR module's; the assistant only presents it.
In practice
EUDR, in conversation
Requests the assistant handles with the tools of the EUDR module (fictitious data).
You
Here is our list of items. Which ones fall within the scope of the EUDR?
Your assistant, via Orki
Out of 214 items, 38 fall under Annex I: 22 cocoa-based, 9 timber, 5 coffee and 2 rubber. The other 176 are not in scope.
You
Which lots are blocked, and what is missing for each one?
Your assistant, via Orki
3 lots out of 18. Cocoa from Côte d'Ivoire: 12 plots not geolocated. Timber from Brazil: supplier statement pending. Coffee from Ethiopia: risk to mitigate before approval.
You
What is the risk level of the countries our cocoa comes from?
Your assistant, via Orki
According to the classification in force in Orki, 3 of your 4 cocoa suppliers are in standard-risk countries and 1 in a low-risk country. The first 3 require a full risk assessment.
You
Add a mitigation action on the soy lot that arrived last week.
Your assistant, via Orki
Action recorded on soy lot 2026-063: documentary audit of the supplier, due by 5 December. You will find it in Orki, on the lot.
The assistant's tools
What your assistant does in the EUDR module
Same access rules as the application: module enabled on the workspace and EUDR role. An auditor stays read-only.
Read
The overview of your compliance.
The workspace summary
Lots, their status and their details
Suppliers and products
Analyse
The two questions that open any due diligence.
Classification of your product codes against Annex I
The risk level of countries of origin
Write, if you allow it
On workspaces where write access is enabled, and according to your EUDR role.
Create lots
Respond to product reviews
Add and close mitigation actions
What stays in your hands
Signing the risk decision, submitting the due diligence statement and inviting suppliers are done in Orki, by the user, never by the assistant.
Understanding MCP
A standard connector between your AI and your Orki data
You don't need to be a developer to use it. Here is what it is, and what happens when your assistant works in Orki.
What is MCP?
MCP (Model Context Protocol) is an open standard published by Anthropic in late 2024 and since adopted by most AI assistants. It defines a single way to connect an assistant to a piece of software.
It is often compared to a USB-C port: the same connection works whatever the assistant, and whatever the tool on the other side.
What difference does it make?
Without MCP, your assistant only knows what you paste into the conversation. With the Orki MCP, it reads your data on the platform, runs calculations, checks a file before import and, if you allow it, saves data.
You stay in the tool you already use, with the model you have chosen.
Who does the calculations?
Orki. The assistant never makes up an emission factor or a result: it calls the platform's tools, which apply the same rules and calculation methods as the application.
A result obtained through the assistant is therefore identical to the one you would read in Orki.
Security and control
Your assistant never has more permissions than you
The Orki MCP acts on behalf of the signed-in user, with exactly the permissions that user has in the application.
Sign-in with your Orki account
The assistant connects through OAuth, the standard for connections between applications. You sign in on Orki, never in the assistant, and no password is ever shared with it.
Your permissions, nothing more
Entities, roles, contributor restrictions, locked workspaces: anything you cannot do in the application, the assistant cannot do either. An auditor stays read-only.
The workspaces you choose
When you connect, you choose which workspaces the assistant can see. A workspace you have not ticked remains invisible to it.
Write access, on authorisation
Read access is granted by default; write access is turned off. You enable it workspace by workspace, and you can withdraw it whenever you like.
Revocable at any time
Connected applications are managed from Orki's settings: one click is enough to cut off an assistant's access.
No extra tokens to pay for
The model runs on your subscription to the assistant. Orki provides the data and the calculations, not the model.
Getting connected
Compatible with the main AI assistants
Claude, ChatGPT, Claude Code, Cursor, Mistral's Le Chat, Copilot in VS Code: any MCP-compatible assistant can connect to Orki. An Orki expert opens your access and sets up the connection with you, on your own workspaces.
The Orki MCP on other modules
Still have questions?
Everything you need to know about the Orki MCP and how to use it day to day.
Book a demoYour EUDR due diligence, in conversation
In the demo, we connect an assistant to an EUDR workspace: classifying a catalogue, tracking lots and risk.
Book a demo