When we first built Om, we needed a way to prioritize ~17K proteins for screening. That internal tool—automated literature review, opportunity scoring, and multiplexed referencing—became Diligence. Today it’s the same system we give customers: the UI provides instant summaries, and the API exposes the exact endpoints we use in production.
Search across the proteome
Start at /diligence/search to look up any emerging target, browse our growing library of protein profiles, and open the Diligence cards that bundle the core sections researchers ask for—clinical trials, therapeutic strategy, disease association, biology, pathway context, and more. Each section links directly to the cited publications so you can verify the evidence without reading hundreds of PDFs.
Request fresh runs when something is missing
If a target is not available yet, use the in-product “Request Diligence Run” flow to notify our team. We’ll review the target and email next steps for running Diligence in Om.
Automate with the API and Wallet Credits you already have
Everything in the UI is mirrored by the API. Call POST /v2/diligence/synthesizeReport for a structured, gene-key-based brief, or run POST /v2/diligence/deep-diligence to generate a fresh, claim-driven diligence report from scratch. For fast ad‑hoc exploration, use POST /v2/diligence/search, /gather, and /crawl. GET /v2/diligence/gene-keys stays free so you can enumerate what we already believe to be true. Wallet Credits power these programmatic workflows, and you can use the pricing page or GET /v2/pricing to inspect current endpoint costs.
Ship diligence faster
Grab an API key, fund your wallet, search the UI to orient on a target, and kick off programmatic workflows when you need Generated Data you can plug into downstream tooling. Every result is citation-backed, auditable, and ready for the next meeting.
