Corti
Corti is a healthcare AI platform for developers, offering a full stack of clinical AI building blocks over a single OAuth 2.0-secured API: real-time speech-to-text (dictation and ambient documentation over WebSocket), clinical text generation and structured/guided documents, AI-assisted medical coding (ICD-10, CPT, OPCS-4, CCAM, OPS and more), fact extraction, an Agentic Framework (A2A protocol with prebuilt medical experts and MCP integration), OpenAI/Anthropic-compatible EU-hosted Corti Models, and an embeddable Corti Assistant clinical scribe. The platform is EU/US data-resident and carries extensive healthcare compliance (SOC 2, ISO 27001/13485/42001, HIPAA, GDPR, EU AI Act, FedRAMP, NHS DTAC/DCB0129). Backed by Atomico and Prosus Ventures.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Corti the way a machine reads it — 13 machine-readable artifacts across 8 APIs, 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 — Corti scores 56.7/100 (developing), with a separate agent-readiness read of 43/100 (agent aware). 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.
How we profile Corti
Each block below is one kind of artifact we hold for Corti. 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.
APIs 8
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Corti Speech to Text API
Real-time, bidirectional stateless dictation over WebSocket, returning live transcripts and detected commands.
Corti Ambient Documentation API
Real-time ambient documentation over WebSocket, returning live transcripts and extracted clinical facts.
Corti Text Generation API
Generate clinical documents and structured/guided documents from interactions and templates.
Corti Medical Coding API
Stateless prediction of ICD-10-CM/PCS, ICD-10 (international/UK/FR/GM), OPCS-4, OPS, CCAM and CPT codes from clinical text.
Corti Agentic Framework API
Build and orchestrate healthcare agents over the A2A protocol with prebuilt medical experts and MCP tool integration.
Corti Models API
OpenAI-compatible (Chat Completions, Responses, Completions, Embeddings) and Anthropic-compatible (Messages) frontier models hosted on EU infrastructure.
Corti Administration API
Programmatically manage customers, users, quotas and usage for a Corti Console project.
Corti Assistant Embedded
Embeddable ambient clinical scribe via Web Component, PostMessage (iframe/WebView) and Window APIs.
Scroll within the panel for all 8 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
corti-mcp.yml
MCP SERVERSecurity 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.
Corti Trust Center
SOC 2, ISO 27001, ISO 27017, ISO 27018, ISO 13485, ISO 42001, ISO 14971, ISO 62366, HIPAA, GDPR, EU AI Act, DORA, NIS2, NHS DSPT, NHS DTAC, NHS DCB0129, FedRAMP, Cyber Essential...
SECURITYScopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Resources
Every other property we hold for Corti — 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 5
Portal, sign-up, and the first successful call
Documentation 4
Reference material describing how the API behaves
Agent Surfaces 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 7
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 7 ·
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 5
Authentication, authorization, and security posture
Operate 5
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/corti · machine-readable index on apis.io