Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.corti.ai/llms.txt

Use this file to discover all available pages before exploring further.

Corti text generation LLMs are specifically designed for use in the healthcare domain. The API endpoints detailed below provide access to different text generation functionality. Selecting the right endpoint is important based on your needs and use case.
Please review the languages page to learn more about languages supported per endpoint and language code to use in API requests.

​
Corti Text Generation Endpoints

Streams

Real-time fact extraction to power intelligent ambient documentation and decision support workflows

FactsR™

Stateless REST endpoint to extract facts from text input

Guided Document Synthesis

Beta
Generate structured, schema-controlled documents on POST /documents — four template-supply paths, interaction-optional

Templates & Sections

Beta
Author, version and publish your own sections and templates as first-class, UUID-addressable resources

Documents Classic

Original POST /interactions/{id}/documents flow with templateKey and inline section overrides. Covers Classic templates & sections too. Planned for deprecation — see the migration guide.

​
What’s new with Guided Documents (Beta)

The Guided Documents surface for documents is a meaningful step up from Classic. Each capability below is net-new with POST /documents + the new authoring API.

Typed, schema-controlled outputs

Define output as string, number, boolean, array or object with named fields[]. Replaces free-text formatRuleOverride with primitives the model is steered to fit.

Author your own sections & templates

First-class, UUID-addressable resources via /documents/sections and /documents/templates. Author every prompt end-to-end instead of overriding Corti-curated keys.

Versioning & publishing

Explicit version + publish lifecycle on every section and template. Iterate freely; previously published versions stay live until you publish a new one.

Inheritance via `inheritFromId`

Create inheriting variants without losing future improvements on fields you didn’t override. Foundation for customer/department/specialty scaling.

Interaction-optional

Supply context (text / transcript / facts) or an interactionId. No longer required to attach to an interaction.

Drift-proof snapshots

Every generation call returns the templateId + templateVersionId it actually used — including auto-generated aggregates for overrides and assemblies.

​
Guided Documents (beta) vs. Classic at a glance

Guided Documents

Endpoint: POST /documents
  • Sections & templates as UUID resources, versioned + publishable
  • Authoring API: /documents/sections, /documents/templates
  • Typed outputSchema for structured outputs
  • inheritFromId for variants
  • Interaction-optional
  • Source-aware: source: corti Standards interleave with source: user
Start with Guided Synthesis or the Customization Cookbook.

Documents Classic

Endpoint: POST /interactions/{id}/documents
  • String templateKey (corti-soap, corti-hpi, …)
  • Read-only Corti library + per-request inline overrides
  • Free-text formatRuleOverride
  • No authoring, no versioning
  • Interaction-scoped
Planned for deprecation when beta moves to general availability. Plan your move via the migration guide.
Classic continues to work today, but will be deprecated as soon as the Guided Documents Beta surface moves into general availability. The exact sunset timeline will be communicated via the upcoming changes log. New integrations should build on Beta.

​
Endpoint Functionality

ConnectionRESTRESTWSSREST
Data processingSynchronousSynchronousSynchronousSynchronous
ArchitectureStateless or Stateful1StatefulStatefulStateless
Text GenDocumentsDocumentsFactsRFactsR
Based on TemplatesYesYesNoNo
Quality Assurancecoming soonGuardrailscoming soonN/A
1 Guided Documents is interaction-optional: supply context (text / transcript / facts) for a stateless call, or supply interactionId to pull facts and transcripts attached to an existing interaction implicitly. The two are mutually exclusive today; combining them is on the roadmap.
Please contact us if you are interested in features that are not listed here, need help determining the best text generation endpoint for your needs, or have questions about how to configure your API requests.