> ## 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.

# Recipe 1 — Use a Corti Standard out of the box

> Reference a curated Corti Standard template by UUID with no overrides — the lightest, fastest production path.

<Badge className="accent-badge" shape="rounded">Beta</Badge>

← Back to [Customization Cookbook](/textgen/customization-cookbook)

**Scenario:** You want a SOAP note, an HPI section, a Plan section — exactly as Corti curates them.

**What you do:**

1. Discover the section/template UUID for your locale via `LIST /documents/sections?lang=en` (filter `source === "corti"` client-side; see [Corti Standards](/textgen/corti-standards#discovery-via-the-api)).
2. Reference the UUID from `POST /documents` using Path 1 (plain `templateRef`).

```json title="POST /documents — Path 1 (plain templateRef)" expandable theme={null}
{
  "outputLanguage": "en-US",
  "interactionId": "<your-interaction-id>",
  "templateRef": {
    "templateId": "<your-template-id>"
  }
}
```

**Why this lever:** Zero side-effects, fastest path. Corti improvements to the Standard propagate automatically — the next call uses the latest published version. These upstream updates are typically **silent** (small prompt refinements and quality improvements ship continuously, like many small API releases); only schema-breaking or significant behavior changes are explicitly communicated.

**When you've outgrown it:** You want a different section title, a different writing style, a tighter `outputSchema`, or one extra section. Move to [Recipe 2](/textgen/customization-cookbook/recipe-2-inherit-corti-standard) (or [Recipe 4](/textgen/customization-cookbook/recipe-4-author-your-own) if you need to fully decouple from the Standard's silent updates).

***

Next: [Recipe 2 — Inherit from a Corti Standard via `inheritFromId`](/textgen/customization-cookbook/recipe-2-inherit-corti-standard)