Eudr

Check up to six production plots for forest loss after 31 December 2020, the cut-off in Regulation (EU) 2023/1115. Takes GeoJSON boundaries, the commodity, and the country of production. Returns a per-plot verdict, the loss years observed, how much of each plot was inspected, and a handle for the underlying satellite evidence. This answers Article 3(a) only: it does not check land tenure, permits, consent, or chain of custody, and it lists those gaps on every response. This has side effects, though it writes nothing to the organisation's records and costs no credits: every call asks emem.dev to make freshly signed measurements, so repeating a check returns the same finding under new signatures, and mints a short-lived evidence handle held on this server for 24 hours, which eudr_fetch_evidence resolves and which a later check will not reproduce.

Retrieve the signed satellite facts behind a completed check, a page at a time, using the `evidence_cid` that check returned. Each entry is a content address that resolves at emem.dev and verifies offline against the responder's key. Use this when someone needs to audit or cite the evidence, not to summarise a result.

Check what each supplier's file is still missing against Article 9(1) of Regulation (EU) 2023/1115, the closed list of information an operator must hold before filing. Returns the unmet items with their article reference and what to request, separating items that block filing from items that merely leave the file incomplete. This is a checklist over the fields you supply; it reads no documents and judges no evidence.

Look up the country benchmark tier under Implementing Regulation (EU) 2025/1093, the Annex I commodity to HS-code mapping under Regulation (EU) 2023/1115, the seaports and airports a consignment can leave or enter through (UN/LOCODE), or which countries actually supply the Union with each commodity and in what volume (UN Comtrade 2023, with World Bank indicator prices). Returns the table this engine evaluates against, with its source and the date it was verified.

Verify a statement receipt: re-derive its content address from the canonical payload and check the ed25519 signature. Use it on a receipt a counterparty hands you. A valid signature establishes who signed and that the bytes are unchanged; it does not establish that the claim inside is true.

Compile and sign an Annex II Due Diligence Statement. This WRITES: it stores a compile task holding the operator and supplier details you pass, and sends the plot geometry, HS code, country and quantity to emem.dev to be measured and independently signed. Operator and supplier identity are not forwarded upstream. Returns a task handle; read the outcome with eudr_get_dds. Nothing is filed with any authority. Confirm the details with the user first. Costs 5 credits from the organisation's wallet (from 30 October 2026, plus 1 for each plot after the first), refunded automatically if the compile fails; every other tool here is free.

Read the state of a compile started by eudr_prepare_dds. While it runs, returns the current state. Once finished, returns the verdict, the receipt's content address and signing key, and the link to the printable statement.

The complete derivation chain behind a compiled statement, in order: polygon to grid addresses, signed measurements, the algorithm and the registries it was pinned against, cell verdicts to a consignment verdict, citations, and which of three independent keys signed what. A stage whose evidence is absent is reported as absent with its reason. Use it when someone asks how a result was reached rather than what it was.

Parse a consignment list into structured shipments ready to check. Accepts a CSV export (the column set eudr.dev publishes) or a GS1 EPCIS 2.0 JSON-LD document. Returns one row per shipment with supplier, commodity, country, quantity and plot boundaries, plus a warning for every row that could not be read and the reason. Nothing is stored and nothing is submitted; this only reads the document you pass.

Export a compiled statement as TRACES NT submission XML, signed Annex II JSON, or plot boundaries as GeoJSON. Exporting is not filing: nothing is submitted to any authority. TRACES export is refused for a non-negligible verdict, because Article 4(1) bars placing those goods and a non-filable assessment must not be handed out as a submission document.

List the Due Diligence Statements already in the signed-in organisation's account, newest first, with verdict, reference, commodity, country, quantity and date. Use this to answer what has been filed, what is outstanding, and what a past consignment concluded, rather than asking the user to re-enter details their account already holds.

Summarise the signed-in organisation's position: how many statements are filable, how many are blocked by a non-negligible verdict, how many are unresolved, broken down by commodity and country, plus outstanding supplier evidence requests. Answers "where do we stand" without enumerating every record.

無需輸入參數。

List the supplier evidence requests this organisation has issued: who was asked, whether they responded, and when each request expires. Answers which suppliers still owe plot boundaries and production details.

無需輸入參數。

Create a one-time link a supplier can use to submit their plot boundaries and production details straight into this organisation's account, without needing an account of their own. This writes: it creates a credential that lets whoever holds the link submit data to you, and returns that link once. Send it only to the intended supplier. No email is sent by this call.

Report this organisation's credit balance, how many signed statements it will cover, and what has been spent. Checking plots, looking up references, assessing supplier gaps and reading traces cost nothing and are always available — only compiling a signed statement draws the balance down. Use this before starting a batch of compiles so the user is not surprised part-way through. The first call for an organisation writes: it opens the wallet, grants the welcome credits and records that grant as the opening ledger line. Every call after that only reads.

無需輸入參數。

Report the Article 11 risk-mitigation plans this organisation has open against flagged shipments: which steps are outstanding, which article each discharges, whether a step needs a person or can be re-run automatically, and what evidence has been recorded. A non-negligible verdict creates an obligation under Article 11 to act before the product is placed on the market; this answers how far that has got. Pass a shipment id for one plan, or omit it for everything still open. Read-only — recording a decision is a deliberate human act and is done on eudr.dev, because Article 11(3) requires mitigation decisions to be documented and demonstrable; eudr.dev records each against the named person who made it, which is our choice rather than the Regulation's wording.

List the organisation's farms and its recent buying decisions (GO / GO WITH CONDITIONS / NEEDS A PERSON / NO-GO per destination), with which carry a recorded outcome and which were overridden. Use it to find a farm id before eudr_decide_lot, or to see how decisions have turned out. Read-only.

無需輸入參數。

Run the organisation's own buying process on a banana lot from one of its farms: every destination in its library gets GO / GO WITH CONDITIONS / NEEDS A PERSON / NO-GO with the chance the whole chain holds, the margin P10/P50/P90, the most the buyer can pay and keep that outcome, the deal zone against the farmer's ask, and what the farmer is told (never the walk-away price). Every default the lot needed is returned as a stated assumption. Banana only; other crops are refused by name. The run is stored as a decision the organisation can later record an outcome against. Send `lot` in the shape of `lot_example` from eudr_procurement_overview. The crop is taken from the farm's own record.

List the farms in this organisation's record: id, name, country, whether a boundary is confirmed and its area in hectares (geodesic, holes out), and how many EU statements were made for each. Read-only.

無需輸入參數。

Add a farm to this organisation's record. A name is enough; give the crop, country and a pin (lat, lon) when known. Give its boundary as `boundary` (a GeoJSON Polygon or MultiPolygon, longitude first), or as `fields`: several field outlines (for example Fields of The World parcels) that are joined into one farm by closing the bunds and tracks between neighbours (`join_m`, default 3 m each way), fields farther apart kept as separate pieces. With a boundary, what follows runs at once: the country from where the land lies when none is given, the forest record warmed, and the land check when the crop is one the EU regulation covers. With only a pin, the mapped fields around it are looked up as suggestions for a person to accept. This writes to the organisation's record.

Set the boundary of a farm already in the record, as `boundary` (GeoJSON Polygon or MultiPolygon) or as `fields` to join into one farm (see eudr_create_farm). It becomes the farm's confirmed boundary, recorded as set by this agent credential, and what follows runs at once: the country from where the land lies, the forest record warmed, the land check. This writes to the organisation's record, and REPLACES any boundary the farm already had: the previous outline stops being the farm's boundary, and because the boundary decides which land is checked, the compliance answers and the area derived from it change with it. The superseded outline is kept in the farm's history and can be read back, but this call does not undo on its own — confirm with the user before overwriting a boundary somebody else set.