Regulatory compliance, in your pipeline.

Get an API key. Send a SMILES to POST /v1/faves/check with the frameworks you need screened. Get back a compliance decision and a receipt URL you can hand to a reviewer. That's the whole workflow. No SDK to install, no schema to learn beyond the request body — just an HTTP call from wherever your pipeline lives.

The API is the product. Here's the actual request and response.

$ curl -X POST https://api.novomcp.com/v1/faves/check \
  -H 'Content-Type: application/json' \
  -H 'Authorization: Bearer ncmcp_...' \
  -d '{
    "smiles": "CC(=O)Oc1ccccc1C(=O)O",
    "frameworks": ["dea", "eu_reach", "pains", "structural_alerts"]
  }'

{
  "smiles": "CC(=O)Oc1ccccc1C(=O)O",
  "name": "aspirin",
  "cleared": true,
  "checks": {
    "dea":               { "flagged": false, "schedule": null },
    "eu_reach":          { "flagged": false, "annex_xvii": [], "svhc": false },
    "pains":             { "flagged": false, "matches": [] },
    "structural_alerts": { "flagged": false, "matches": [] }
  },
  "audit": {
    "call_id":     "cal_01HRE8ZQK4M7X...",
    "ruleset_ver": "faves-v4.1.3",
    "retention":   "7y",
    "receipt_url": "https://api.novomcp.com/v1/faves/audit/cal_01HRE8ZQK4M7X..."
  }
}

Every call produces a receipt_url with the ruleset version, tamper-evident hash, and retention pointer. That's the record your compliance team hands the auditor — not a screenshot of a report, an addressable immutable receipt.

Every major dictionary a regulated submission touches.

Immutable audit trail, drift monitoring, IQ / OQ / PQ, and SLA.