diff --git a/fern/providers/observability/langfuse.mdx b/fern/providers/observability/langfuse.mdx
index bc3f853cf..2d2784916 100644
--- a/fern/providers/observability/langfuse.mdx
+++ b/fern/providers/observability/langfuse.mdx
@@ -8,6 +8,8 @@ slug: providers/observability/langfuse
 
 Vapi natively integrates with Langfuse, allowing you to send traces directly to Langfuse for enhanced telemetry monitoring. This integration enables you to gain deeper insights into your voice AI applications and improve their performance and reliability.
 
+This page covers connecting Langfuse to Vapi. For Langfuse's own guide to working with traces once they arrive, see the [Langfuse tracing documentation](https://langfuse.com/docs/tracing).
+
 <Frame>
   <div class="video-embed-wrapper">
     <iframe
@@ -50,10 +52,16 @@ Under the **Observability Providers** section, you'll find an option for **Langf
 - **Public Key**
 - **Host URL** (US data region: `https://us.cloud.langfuse.com`, EU data region: `https://cloud.langfuse.com`)
 
+For a self-hosted server, when you finish editing the Host URL, Vapi reads your Langfuse server's version from its unauthenticated `{Host URL}/api/public/health` endpoint, and the **Server version** row fills in with what it found. You can also trigger the check yourself with **Check server version**. **Save** stays disabled until a version is resolved, so every saved self-hosted credential knows which server it points at. Editing the Host URL clears the version, because a version belongs to the server it was read from.
+
+A Langfuse Cloud Host URL needs no version: Cloud is recognized by its hostname, so **Save** is available right away and nothing is checked when you leave the field. **Check server version** still reads Cloud's version if you want to see it.
+
+If your `/api/public/health` endpoint is hidden behind a proxy or firewall, a **Server version** field appears so you can state the version yourself (for example `3.63.0`). The Host URL itself must still use `https://` and resolve to a public address. Vapi only sends your keys over an encrypted connection, and it probes and exports from the public internet, so an `http://` Host URL, or one that resolves to a loopback, link-local, or private-network address, is refused regardless of the version you enter.
+
 Click **Save** to update your credentials.
 
 <Frame caption="Langfuse in Vapi Integrations.">
-  <img src="https://langfuse.com/images/docs/vapi-integration-credentials.png" alt="Langfuse Credentials form under Observability Providers in the Dashboard with Secret Key, Public Key, and Host URL fields" />
+  <img src="../../static/images/providers/langfuse-credentials.png" alt="Langfuse Credentials form under Observability Providers in the Dashboard with Secret Key, Public Key, and Host URL fields, a Server version row with a Check server version button, and a Save button" />
 </Frame>
 
 </Step>
@@ -72,11 +80,68 @@ Example trace in Langfuse: https://cloud.langfuse.com/project/cloramnkj0002jz088
 
 <Step title="Evaluate and Debug your Agent">
 
-To make the most out of this integration, you can now use Langfuse's [evaluation](https://langfuse.com/docs/scores/overview) and [debugging](https://langfuse.com/docs/analytics/overview) tools to analyze and improve the performance of your voice AI agents. 
+To make the most out of this integration, you can now use Langfuse's [evaluation](https://langfuse.com/docs/scores/overview) and [debugging](https://langfuse.com/docs/analytics/overview) tools to analyze and improve the performance of your voice AI agents.
+
+If you are on Langfuse Cloud and already run LLM-as-a-judge evaluators, note that Langfuse retires its legacy evaluators on November 16, 2026; their [migration guide](https://langfuse.com/faq/all/llm-as-a-judge-migration) covers the upgrade, and their UI walks you through it.
 
 </Step>
 </Steps>
 
+## Server Version Detection and SDK Routing
+
+Vapi exports traces over two paths: the modern OpenTelemetry (OTLP) path of the Langfuse JS SDK v5, and the legacy v3 ingestion API. Which one your credential uses follows the Langfuse server version resolved when you saved it:
+
+- **Langfuse Cloud** always uses the OTLP path. Cloud is recognized by its hostname, so this applies to credentials saved at any time, including before this feature existed. All Cloud regions are supported: `us.cloud.langfuse.com`, `hipaa.cloud.langfuse.com`, `jp.cloud.langfuse.com`, and `cloud.langfuse.com`.
+- **Self-hosted on 3.63 or later** uses the OTLP path, once the credential has a detected server version.
+- **Self-hosted on versions earlier than 3.63**, and **any self-hosted credential with no detected version**, continues on the legacy v3 ingestion API.
+
+<Note>
+If you self-host and saved your credential before version detection existed, it has no stored version, so your traces stay on the legacy path. That is a working path and nothing is interrupted, but upgrading your Langfuse server alone will not move you: **re-save the credential in the Vapi dashboard** so Vapi reads your server's current version. Nothing re-probes on its own, and the stored version changes only when you save again.
+</Note>
+
+Self-hosted Langfuse v3 remains supported through the upstream v3 patch window ending January 31, 2027.
+
+<Note>
+**Langfuse Cloud removes its legacy ingestion API and legacy features on November 16, 2026**, in every region. Vapi's own export is handled: Cloud credentials use the OTLP path, so your traces keep arriving. The one thing that may need your attention is in your Langfuse project rather than in Vapi: if you use Langfuse's legacy LLM-as-a-judge evaluators, migrate them before that date. See Langfuse's [LLM-as-a-judge migration guide](https://langfuse.com/faq/all/llm-as-a-judge-migration) and their [v4 upgrade guide](https://langfuse.com/faq/all/upgrade-to-langfuse-v4). Self-hosted servers are unaffected by this date and upgrade on your own schedule.
+</Note>
+
+## Trace IDs and Call Correlation
+
+On the OTLP export path, a trace ID is an OpenTelemetry trace ID: exactly 32 hexadecimal characters. A Vapi call ID is a UUID, so it cannot be used as a trace ID directly. Vapi therefore **derives** the trace ID from the call ID, as the first 32 hex characters of its SHA-256 hash. The derivation is deterministic, so the same call always produces the same trace ID.
+
+Every trace also carries the call ID as `metadata.callId`, which is the recommended way to correlate. Filtering and searching by call ID in the Langfuse UI is unaffected.
+
+<Warning>
+On the legacy v3 path, a trace's ID *was* the Vapi call ID verbatim. If your own code reads or writes Langfuse traces by using a call ID as the trace ID, for example scoring a trace from an end-of-call webhook, update it to either filter on `metadata.callId` or compute the derived ID.
+</Warning>
+
+Computing the derived trace ID:
+
+<CodeBlocks>
+```typescript title="TypeScript"
+import { createHash } from 'crypto';
+
+const traceId = createHash('sha256').update(callId).digest('hex').slice(0, 32);
+```
+```python title="Python"
+import hashlib
+
+trace_id = hashlib.sha256(call_id.encode()).hexdigest()[:32]
+```
+</CodeBlocks>
+
+## Troubleshooting
+
+**The Host URL redirects to another origin.** Host URLs that redirect elsewhere are refused, because trace exports do not follow redirects: the save would succeed and the exports would silently go nowhere. For example, `https://eu.cloud.langfuse.com` redirects to `https://cloud.langfuse.com`, so use `https://cloud.langfuse.com` directly, which is Langfuse's recommended base URL for EU-region projects and does not change where your data is stored. The error message names the URL to use instead.
+
+**The Host URL must use HTTPS and resolve to a public address.** Vapi only sends your keys over an encrypted connection, so an `http://` Host URL is refused when you save, with a message asking for an `https://` one. Vapi also probes and exports from the public internet, so a Host URL that resolves to a loopback, link-local, or private-network address is refused. Entering a server version by hand bypasses neither rule. A credential saved earlier with an `http://` Host URL keeps sending traces over the legacy v3 ingestion API, but saving it again requires an `https://` Host URL.
+
+**Vapi could not detect your server's version.** This means `{Host URL}/api/public/health` did not answer, or answered without a version, which is typical when a proxy or firewall sits in front of it. Enter your server's version yourself in the **Server version** field, as `major.minor.patch` exactly how your server's health endpoint reports it (for example `3.63.0`).
+
+**Traces stop appearing during calls.** On the OTLP path, if a call's trace cannot be started or delivered, for example because your server became unreachable or was upgraded across the 3.63 boundary, Vapi writes an error into that call's logs with a link to the [Integrations page](https://dashboard.vapi.ai/settings/integrations). Re-save your Langfuse credential there so Vapi reads your server's current version; nothing re-detects it in the background.
+
+**No traces from PCI calls.** When an assistant has [`compliancePlan.pciEnabled`](/security-and-privacy/pci) set, Vapi sends nothing from its calls to Langfuse: no conversation traces and no tool calls. This applies on both export paths.
+
 ## Enrich Traces
 Vapi allows you to enrich Langfuse traces by integrating [Metadata](https://langfuse.com/docs/tracing-features/metadata) and [Tags](https://langfuse.com/docs/tracing-features/tags).
 
@@ -99,6 +164,10 @@ Examples:
 - Store user segments ("user_type": "beta_tester")
 - Log environment details ("env": "production")
 
+<Note>
+On the Langfuse JS SDK v5 export path, each top-level metadata key becomes one trace attribute, and nested values are serialized as JSON strings. A trace keeps at most 512 metadata keys; any keys beyond the first 512 are dropped. Vapi's own identifiers, such as the call ID, are added separately and are always kept, even if your metadata uses the same key name. Keep metadata to a small set of filterable values and store large payloads elsewhere, referencing them by ID.
+</Note>
+
 **Tags**
 
 Use the [`assistant.observabilityPlan.tags`](/api-reference/assistants/create#request.body.observabilityPlan.tags) field to add searchable labels.
diff --git a/fern/static/images/providers/langfuse-credentials.png b/fern/static/images/providers/langfuse-credentials.png
new file mode 100644
index 000000000..6f3169006
Binary files /dev/null and b/fern/static/images/providers/langfuse-credentials.png differ