Skip to content
FAVES API · Hosted

Compliance screening, in your pipeline.

One API call per molecule returns its regulatory status across eight frameworks, 1,585 structural alerts, predicted absorption and brain penetration, and prior-art disclosure, each field with its source. Informational screening for early discovery: it shows a chemist what to examine before money is spent on a molecule.

How you use it

Get an API key. Send a SMILES and its context, the intended use and the jurisdiction, to POST /v1/tools/check_compliance. The response carries a verdict (PROCEED, STOP or CAUTION), the risk factors behind it, recommendations, and each layer's result with its provenance. Approved drugs on the FDA whitelist return PROCEED, with any structural alerts reported as context. Inside the open engine, the check_compliance tool calls the same API.

What one call returns

Four layers, each with its source.

Regulatory status
DEA scheduling, including structural relatives of scheduled compounds; FDA approval; EPA, EU REACH, the Australian schedule, and the CWC, BTWC and OPCW treaty frameworks. Which apply is set by the intended use and jurisdiction you send.
Structural alerts
1,585 SMARTS patterns from published catalogs (PAINS, Brenk, NIH, ZINC, ChEMBL), run with RDKit FilterCatalog. Alerts are flags for a chemist to examine, not verdicts.
Pharmacokinetic class
BOILED-Egg classification: predicted gut absorption and blood–brain barrier penetration.
Prior art
Exact-structure disclosure in public chemistry databases, resolved by InChIKey.

Context routes each call: intended use (pharmaceutical, research, industrial, agricultural, cosmetic), jurisdiction (US, EU, UK, CA, AU, JP, CN, or global treaties), and an optional therapeutic area.

What stands behind it

Validated, reproducible, and documented.

Validated before it was released

Risk-based GAMP classification, with acceptance criteria written before testing. The recorded run scored 341 of 342. The one miss was a wrong SMILES for cortisol in the approved-drug whitelist; the full 102-compound benchmark caught it, and change control fixed it.

Reproducible outside the service

20 of 20 compounds return identical results from the deployed service and from a separate local RDKit install. The benchmark data, validation reports, and the scripts behind them are public.

Seven governance documents

Intended use, risk and software classification, validation, audit, change control, user-interface guidance, and a technical overview. Summarized in the preprint; full versions on request.

An audit trail on every call

A three-layer audit trail, two layers of which cannot be skipped. Latency is about 0.45 s per call with a cached prior-art answer and about 3.1 s with a live PubChem lookup (May 2026 benchmark).

Limits

Peer-reviewable

FAVES V4 is documented in an open preprint on ChemRxiv. The supporting-information repo holds the benchmark data, the validation and latency reports, and the scripts that produced them.

Compliance screening · Contact

Screen your shortlist with FAVES.

Access is granted per pipeline. Describe the pipeline and NovoMCP scopes the fit.