For developers: EUDR GeoJSON validation in your pipeline
Validate, fix and file EUDR geolocation data from your own software: a REST API with OpenAPI, an MCP server, and a command-line tool for CI.
If your software produces or receives EUDR geolocation files (an ERP, a traceability platform, a trading system), you want the same checks the Information System applies, before a user hits submit.
The REST API
For software that receives files from users or suppliers: /validate, /fix,
/convert, /report and /forest, plus projects and due diligence statements, filed
with the EU Information System from a saved file. Described in OpenAPI 3.1 for client
generators, with stable error codes and rate-limit headers. Files sent for checking are
processed and not stored. See the API reference.
The MCP server
For AI assistants (Claude, Cursor, VS Code): the same operations as tools, locally from the command-line tool (your files stay on your computer) or hosted, with your projects. See MCP setup.
The command-line tool
eudr-check runs the same rule registry as the web checker, on your machine:
eudr-check plots.geojson --json
- JSON output with the file's SHA-256, the rule-set version, and for each finding its rule id, slug, severity, message, JSON pointer, character offsets, line and column, and source citations.
- Exit codes for CI: 0 no errors, 1 errors, 2 unreadable input;
--strictfails on warnings too. - Non-GeoJSON input: KML, shapefiles, GPX, CSV, converted first, with every conversion decision reported.
- Forest in 2020 and loss since, with
--forest: each plot's share of forest on the JRC's map, and the 2020 forest lost there since on Hansen's map, in the output and the JSON. The only option that uses the network; it asks for fixed squares of the maps, never the plots.
See the CLI documentation. The tool is not available for download yet.
Stable rule ids
Every rule has a permanent id (GEOM-003) and slug (self-intersection); see
the rule reference. Build on the ids; the titles and messages may be
reworded.
The JSON is the same everywhere: the CLI's --json, the API's /validate and the MCP
tools' structured results.
Which plan
The command-line tool and its local MCP server run on your machine and are not metered. The REST API and the hosted MCP server are on Team (60 requests a minute, 2,500 distinct plots a month) and Consultant (120 requests a minute, 10,000 distinct plots a month), with projects, supplier links, monitoring webhooks and statement filing available through the same API. See pricing.