Latent
Latent (Latent Health) is an enterprise pharmacy intelligence platform for health systems, built around a clinical agentic engine that reads the chart, reasons over payer policy and drug labels, and acts inside the electronic health record. The platform spans four modules — Identify (care-gap identification, eligibility screening, site-of-care routing), Access (prior authorization, clinical review, appeals generation, benefit routing, payer outreach), Capture (340B eligibility auditing, leakage analytics, financial dashboards), and Engage (patient outreach, queue management, outcomes analytics). Latent is chart-native and EHR agnostic, integrating with Epic, Cerner and others, and is used by more than 45 health systems including Ochsner Health, MetroHealth, Yale New Haven Health, St. Luke's Health System and Henry Ford Health, serving over two million patients annually. Founded by Sriram Somasundaram and Rishabh Jain, the company has raised $80M from Spark Capital, Transformation Capital, McKesson Ventures, Conviction, General Catalyst and Y Combinator. Latent publishes no public developer API, documentation, or SDKs; its integration surface is delivered through EHR-native deployment with health-system customers, and its security posture is published on a Vanta-hosted trust center with HIPAA-compliant data handling.
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 Latent the way a machine reads it — 2 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 — Latent scores 20.9/100 (emerging), with a separate agent-readiness read of 0/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 Latent
Each block below is one kind of artifact we hold for Latent. 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.
Security Posture 2
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.
Resources
Every other property we hold for Latent — 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.
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 1
Pagination, idempotency, versioning, errors, and events
Access & Security 3
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 7
The organization behind the API
Scroll within the panel for all 7 ·
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/latent · machine-readable index on apis.io