OpenEvidence
OpenEvidence is a clinical decision-support search platform that uses generative AI grounded in peer-reviewed medical literature to answer clinical questions for verified clinicians. The product is free for U.S. licensed clinicians and is monetized through pharmaceutical advertising; partnerships include the New England Journal of Medicine, JAMA, NCCN, and the Cochrane Library. As of 2026 it serves more than 860,000 verified clinicians. OpenEvidence does not currently expose a public self-service developer API.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles OpenEvidence the way a machine reads it — 12 machine-readable artifacts, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — OpenEvidence scores 20.9/100 (emerging), with a separate agent-readiness read of 10/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile OpenEvidence
Each block below is one kind of artifact we hold for OpenEvidence. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
Features 6
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Evidence-Grounded Search
AI-powered medical search that returns answers grounded in peer-reviewed medical literature with inline citations.
Voice Mode
Hands-free voice interface allowing clinicians to ask clinical questions and receive spoken, evidence-based answers across web and mobile.
Visits
Real-time clinical intelligence delivered during the patient visit.
AI Medical Coding
Generative-AI feature that supports medical coding workflows.
Clinician Verification
Account access restricted to verified U.S. licensed healthcare professionals.
Mobile and Web
Available as web and mobile applications, free for verified clinicians.
Security Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Use Cases 3
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Point-of-Care Decision Support
Clinicians query OpenEvidence at the point of care for diagnostic, therapeutic, and management questions.
Medical Education
Use by medical residents and trainees for evidence lookup.
Coding and Documentation
AI medical coding workflows for revenue-cycle support.
Resources
Every other property we hold for OpenEvidence — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 2
Portal, sign-up, and the first successful call
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 5
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Company 8
The organization behind the API
Scroll within the panel for all 8 ·
Other 3
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/openevidence · machine-readable index on apis.io