RETROSYNTHESIS · ROUTE AUDITING · PURE RUST

Routes you can
inspect locally.

RENKIN is an open-source retrosynthesis planner and route auditor. Search from a target, or inspect a route from another planner without uploading molecular structures.

Try the included route JSON sample in a few minutes. It is processed in your browser and is not uploaded to RENKIN servers.

Start with a target or a route

Planner — start with a targetInput: a target molecule. Output: candidate routes to a declared stock.
Auditor — start with a routeInput: an exported route file. Output: a local JSON report with checks and evidence boundaries.
Inputroute file
Local audityour machine
JSON / reportkeep with input

PUBLISHED TEST CASE / REDUCED OUTPUT

One input, one local audit, one inspectable report

This route is generated from the target below, then audited with RENKIN’s default standard policy.

1 / Input

$ renkin --target
  CCOC(=O)c1ccccc1 --depth 1
  > route.json

2 / Local audit

$ renkin audit-route route.json
  --format auto --output json
  > audit-report.json

3 / Report excerpt

{
  "source_format": "json",
  "audit_manifest": { "policy": "standard" },
  "routes": [{
    "status": "partial",
    "route_tree_parseable": true,
    "stock_validation": { "status": "not_evaluable" }
  }]
}

No stock is supplied in this example, so the report retains a partial result and an explicit not-evaluable stock check. That is a report boundary, not an experimental conclusion.

One local audit pipeline.

AiZynthFinder · Syntheseus · SynPlanner · RENKIN

01 / AUDIT

Audit a route, not a claim

Bring a route from RENKIN, AiZynthFinder, Syntheseus, or SynPlanner. The local report keeps structural checks, stock coverage, forward replay, provenance, and missing evidence separate.

Methodology & limitations

02 / EVIDENCE

Keep the boundary visible

Pass, fail, partial, and not evaluable are not interchangeable. A route audit is not experimental validation, and a missing condition does not become a prediction.

Methodology & limitations

03 / PLAN

Plan from a target when that is the task

RENKIN provides template- and constraint-based A* / AND-OR search, stock-aware scoring, and forward validation. Search output still needs a declared stock, protocol, and experimental review.

Methodology & limitations

QUICK START / AUDIT

A minimal, reproducible audit

This example reads an AiZynthFinder route file and prints the reported audit summary. Use the matching format for Syntheseus, SynPlanner, or RENKIN routes.

The input route stays local. Private stock and policy files can also remain local.

import json, renkin

report = json.loads(
  renkin.audit_route(
    open("trees.json").read(),
    format="aizynthfinder",
  )
)
print(report["summary"])

Practical guides

Use casesRoute auditQuickstartFormatsFAQLimitationsComparison method

CITATION & REPRODUCIBILITY

Cite the version and the protocol

Current citation metadata identifies RENKIN v1.0.9, released 2026-09-22. Preserve the audit manifest and the stock/template configuration in reproducible reports.