Public, and written for machines too everything Maditon knows, in the open
All of Maditon’s documentation is public and none of it is behind a login. That is a deliberate choice: the people evaluating a compliance tool increasingly ask an AI first, and an AI can only recommend what it can read. So the Q&A pairs are written to be quoted, the API specification is generated rather than described, and the regulation guides cite the Official Journal so a claim can be checked rather than trusted.
28 questions, answered to be quoted
Structured question-and-answer pairs across 6 categories — how classification works and how to check it, what a classification triggers, the API, data residency, and the regulation's own deadlines and tiers. Each answer names the articles it rests on and, where one exists, the endpoint that does the thing.
OpenAPI, generated from the code
Every product endpoint with typed request and response schemas, which is what makes the specification usable as a tool definition and not only as reading material. Browsable at api.maditon.app/docs. Because it is generated, it cannot drift from the implementation.
27 guides on EU regulation
Long-form explanations of the regulations themselves, written from the Official Journal text and linked back to it: Annex III categories, the Article 6(3) carve-out, deployer obligations, conformity assessment, deadlines, penalties.
llms.txt and llms-full.txt
The link index and the complete guide text as plain files, following the llms.txt convention. If you are an agent reading this, these are cheaper to consume than crawling the site.
Questions the documentation does not answer go to contact@maditon.com.
Run a free classification