REFERENCE / FORMATS

Supported route formats

A route file is evidence only when its representation, origin, and missing fields are clear. Select the adapter that matches the producer.

Planner-specific input, tool-neutral audit

RENKIN can inspect routes from RENKIN, AiZynthFinder, Syntheseus, and SynPlanner workflows through their matching formats.

Keep original source material

Preserve the original file and identify its originating tool and version. Conversion can discard information, so record it as part of the audit context.

Treat unknown fields honestly

If a field needed for a check is absent, the report should retain not_evaluable rather than infer a value.

FAQ

Questions before you start

Is every external route file automatically compatible?

No. Choose a documented adapter and check the report for fields that could not be evaluated.

Can formats be compared directly?

Only after the route representation and audit conditions have been made comparable.