diff --git a/.claude/rules/mdx-mechanics.md b/.claude/rules/mdx-mechanics.md
index 0f008da7d3..6ab91380e7 100644
--- a/.claude/rules/mdx-mechanics.md
+++ b/.claude/rules/mdx-mechanics.md
@@ -41,6 +41,14 @@ Every page is also served as plain Markdown (append `.md` to its URL to preview)
 - Wrap human-only material in `<llms-ignore>`: UI click-throughs, marketing CTAs, decorative or theme-duplicate images, interactive widgets (`VoiceWidget`). Where a programmatic equivalent exists (CLI/API), give it to agents in a paired `<llms-only>` block — UI steps for humans, commands for agents.
 - `noindex: true` (frontmatter) drops a page from llms.txt and search engines; `hidden: true` (nav yml) also removes it from the sidebar.
 
+Format visibility blocks consistently:
+
+- Put opening and closing tags at column 0, with blank lines around the block and around Markdown inside it.
+- Wrap a complete block component or complete passage, never only an opening tag, caption, or sentence fragment.
+- When a human component contains unique information, put `<llms-ignore>` first and its `<llms-only>` equivalent immediately after it.
+- A standalone `<llms-ignore>` is appropriate when nearby prose already contains the component's meaning, or when the content is decorative, duplicated, or interactive-only.
+- Keep both tags paired rather than self-closing. `<llms-ignore>` changes LLM endpoints, not access control: the content still renders on the site and is available to site search and Ask Fern.
+
 ## Code, links, media
 
 - Every fence declares a language. Label with `title="…"` where a filename or variant helps; highlight lines `{6,9}` and keep highlights aligned across parallel language examples. Mermaid fences render natively.
diff --git a/fern/products/apis/pages/core/overview.mdx b/fern/products/apis/pages/core/overview.mdx
index 808ed445ef..566e0e286d 100644
--- a/fern/products/apis/pages/core/overview.mdx
+++ b/fern/products/apis/pages/core/overview.mdx
@@ -46,8 +46,18 @@ For developers who prefer working in Postman, we maintain an official collection
 
 Click **Run in Postman** to fork the collection into your own Postman workspace.
 
+<llms-ignore>
+
 [<img src="https://run.pstmn.io/button.svg" alt="Run In Postman" style={{ width: "128px", height: "32px" }} />](https://god.gw.postman.com/run-collection/16445495-86c9916b-baa8-4bb3-b62d-d4ae86b12d61?action=collection%2Ffork&source=rip_markdown&collection-url=entityId%3D16445495-86c9916b-baa8-4bb3-b62d-d4ae86b12d61%26entityType%3Dcollection%26workspaceId%3D4f34e511-485e-4462-a432-20fbc2d1db33)
 
+</llms-ignore>
+
+<llms-only>
+
+[Open the SignalWire REST API collection in Postman](https://god.gw.postman.com/run-collection/16445495-86c9916b-baa8-4bb3-b62d-d4ae86b12d61?action=collection%2Ffork&source=rip_markdown&collection-url=entityId%3D16445495-86c9916b-baa8-4bb3-b62d-d4ae86b12d61%26entityType%3Dcollection%26workspaceId%3D4f34e511-485e-4462-a432-20fbc2d1db33).
+
+</llms-only>
+
 ### Set your credentials
 
 Open the collection's **Variables** tab and fill in the three values from the [API pane](https://my.signalwire.com?page=credentials) of your SignalWire Dashboard:
diff --git a/fern/products/call-flow-builder/pages/core/overview.mdx b/fern/products/call-flow-builder/pages/core/overview.mdx
index aac80c66e0..984a92d4ba 100644
--- a/fern/products/call-flow-builder/pages/core/overview.mdx
+++ b/fern/products/call-flow-builder/pages/core/overview.mdx
@@ -19,10 +19,14 @@ It features a simple drag-and-drop interface for creating complex call flows wit
 All elements of the call flow are represented as nodes in a tree structure.
 You can easily add, remove, and rearrange elements in the call flow using the visual interface.
 
+<llms-ignore>
+
 <Frame caption="A sample Call Flow showcasing input-gathering, recording, AI Agent, and TTS features.">
   ![A sample call flow created with Call Flow Builder, showing connections between nodes.](/assets/images/call-flow/sample-flow.webp)
 </Frame>
 
+</llms-ignore>
+
 Add or remove any element from the call flow by dragging it into the desired location,
 and define links between them using the connection lines.
 
@@ -46,6 +50,8 @@ To get started with Call Flow Builder, open the **Tools** tab in the left menu o
 
 Check out this brief demo to see how to add, configure, and connect nodes in Call Flow Builder.
 
+<llms-ignore>
+
 <iframe
   src="https://www.youtube.com/embed/ZPnwEKOhYH4?si=Q1cEQi9RrG6L6VZw"
   title="YouTube video player"
@@ -56,6 +62,14 @@ Check out this brief demo to see how to add, configure, and connect nodes in Cal
   style="width: 100%; aspect-ratio: 16/9;">
 </iframe>
 
+</llms-ignore>
+
+<llms-only>
+
+The [Call Flow Builder demonstration](https://www.youtube.com/watch?v=ZPnwEKOhYH4) shows how to add, configure, and connect nodes on the canvas.
+
+</llms-only>
+
 ### Creating a New Call Flow
 
 To create a new call flow, click on the `Add New` button in the Call Flow Builder section of the Dashboard.
@@ -63,10 +77,14 @@ From here, you can give your call flow a name, and then click `Save` to create t
 After creating the call flow, the Call Flow will show up in the list of call flows in the Dashboard.
 
 
+<llms-ignore>
+
 <Frame caption="Creating a new Call Flow." ogImage>
   ![Creating a new Call Flow in the SignalWire Dashboard.](/assets/images/call-flow/create_flow.webp)
 </Frame>
 
+</llms-ignore>
+
 
 ---
 
@@ -75,10 +93,14 @@ After creating the call flow, the Call Flow will show up in the list of call flo
 Once a Call Flow has been created, you can click on the `More Options` button to open the Call Flow Builder interface.
 From here, click on the `Edit` option to open the Call Flow Builder page.
 
+<llms-ignore>
+
 <Frame caption="Editing a Call Flow.">
   ![Clicking on the edit option for a Call Flow.](/assets/images/call-flow/edit_flow.webp)
 </Frame>
 
+</llms-ignore>
+
 
 #### Add a node
 When you first open a new Call Flow, you will see a canvas with a single node:
@@ -94,10 +116,14 @@ Starting with the [Handle Call](/docs/call-flow-builder/reference/handle-call) n
 clicking and dragging from the output connector (right side of node) to the input connector (left side of node) of another node.
 You will see an arrow connecting the two nodes, indicating that they are connected.
 
+<llms-ignore>
+
 <Frame caption="Adding a new node to a Call Flow.">
   ![Adding a new node to a Call Flow.](/assets/images/call-flow/add_node.webp)
 </Frame>
 
+</llms-ignore>
+
 ---
 
 #### Configure nodes
@@ -105,10 +131,14 @@ Some nodes have configuration options that can be set by clicking on the node.
 This will open a configuration panel where you can set the options for that node.
 For example, the [Play Audio or TTS](/docs/call-flow-builder/reference/play-audio-or-tts) node allows you to select an audio file or enter text to be played to the caller.
 
+<llms-ignore>
+
 <Frame caption="Configuring a node in a Call Flow.">
   ![Configuring a node in a Call Flow.](/assets/images/call-flow/configure_node.webp)
 </Frame>
 
+</llms-ignore>
+
 ---
 
 #### Delete a node
@@ -116,8 +146,10 @@ For example, the [Play Audio or TTS](/docs/call-flow-builder/reference/play-audi
 To delete a node, you can click on the delete icon located on the right side of the node.
 Additionally, you can delete a node if they have configuration options open by clicking the `Delete node` button in the configuration panel.
 
+<llms-ignore>
+
 <Frame caption="Deleting a node from a Call Flow.">
   ![Deleting a node from a Call Flow.](/assets/images/call-flow/delete_node.webp)
 </Frame>
 
-
+</llms-ignore>
diff --git a/fern/products/compatibility-api/pages/cxml/voice/conference-noun.mdx b/fern/products/compatibility-api/pages/cxml/voice/conference-noun.mdx
index 9f1d196734..0fba947c21 100644
--- a/fern/products/compatibility-api/pages/cxml/voice/conference-noun.mdx
+++ b/fern/products/compatibility-api/pages/cxml/voice/conference-noun.mdx
@@ -241,8 +241,18 @@ You can expect several parameters to be present in the request associated to the
 
 #### Request parameters for the `recordingStatusCallback` URL  [#conference_recordingStatusCallback]
 
+<llms-ignore>
+
 <WebhookPayloadSnippet webhook="recordingStatusCallback" />
 
+</llms-ignore>
+
+<llms-only>
+
+See the [Recording status callback reference](/docs/compatibility-api/rest/recordings/webhooks/recording-status-callback) for the request fields sent to `recordingStatusCallback`.
+
+</llms-only>
+
 
 
 
diff --git a/fern/products/compatibility-api/pages/cxml/voice/dial.mdx b/fern/products/compatibility-api/pages/cxml/voice/dial.mdx
index ac7ae88c3a..1316b7413c 100644
--- a/fern/products/compatibility-api/pages/cxml/voice/dial.mdx
+++ b/fern/products/compatibility-api/pages/cxml/voice/dial.mdx
@@ -147,8 +147,18 @@ The `record` attribute allows for recordings in **mono-channel** or **dual-chann
 
 #### Request parameters for `recordingStatusCallback`  [#dial_recordingStatusCallback]
 
+<llms-ignore>
+
 <WebhookPayloadSnippet webhook="recordingStatusCallback" />
 
+</llms-ignore>
+
+<llms-only>
+
+See the [Recording status callback reference](/docs/compatibility-api/rest/recordings/webhooks/recording-status-callback) for the request fields sent to `recordingStatusCallback`.
+
+</llms-only>
+
 ## Examples
 
 ### A simple dial
diff --git a/fern/products/compatibility-api/pages/cxml/voice/number-noun.mdx b/fern/products/compatibility-api/pages/cxml/voice/number-noun.mdx
index 456974bdd0..38b91333df 100644
--- a/fern/products/compatibility-api/pages/cxml/voice/number-noun.mdx
+++ b/fern/products/compatibility-api/pages/cxml/voice/number-noun.mdx
@@ -54,8 +54,18 @@ The `statusCallbackEvent` attribute has the following call status values:
 
 ### Request parameters for the `statusCallback` URL  [#number_statusCallback]
 
+<llms-ignore>
+
 <WebhookPayloadSnippet webhook="voiceStatusCallback" />
 
+</llms-ignore>
+
+<llms-only>
+
+See the [Voice status callback reference](/docs/compatibility-api/rest/calls/webhooks/voice-status-callback) for the request fields sent to `statusCallback`.
+
+</llms-only>
+
 ## Examples
 
 ### Dialing an extension
diff --git a/fern/products/compatibility-api/pages/cxml/voice/record.mdx b/fern/products/compatibility-api/pages/cxml/voice/record.mdx
index b33d52aa4c..344e63c87f 100644
--- a/fern/products/compatibility-api/pages/cxml/voice/record.mdx
+++ b/fern/products/compatibility-api/pages/cxml/voice/record.mdx
@@ -104,13 +104,33 @@ The `action` request contains the [Standard Request Parameters](/docs/compatibil
 
 #### Request parameters for `recordingStatusCallback`  [#record_recordingStatusCallback]
 
+<llms-ignore>
+
 <WebhookPayloadSnippet webhook="recordingStatusCallback" />
 
+</llms-ignore>
+
+<llms-only>
+
+See the [Recording status callback reference](/docs/compatibility-api/rest/recordings/webhooks/recording-status-callback) for the request fields sent to `recordingStatusCallback`.
+
+</llms-only>
+
 
 #### Request parameters for `transcribeCallback`  [#record_transcribeCallback]
 
+<llms-ignore>
+
 <WebhookPayloadSnippet webhook="transcriptionStatusCallback" />
 
+</llms-ignore>
+
+<llms-only>
+
+See the [Transcription status callback reference](/docs/compatibility-api/rest/recording-transcriptions/webhooks/transcription-status-callback) for the request fields sent to `transcribeCallback`.
+
+</llms-only>
+
 ## Nesting
 
 No other verbs can be nested within `<Record>` and you cannot nest `<Record>` within any other verbs.
diff --git a/fern/products/compatibility-api/pages/cxml/voice/sip-noun.mdx b/fern/products/compatibility-api/pages/cxml/voice/sip-noun.mdx
index 6099d99c16..882fe712ca 100644
--- a/fern/products/compatibility-api/pages/cxml/voice/sip-noun.mdx
+++ b/fern/products/compatibility-api/pages/cxml/voice/sip-noun.mdx
@@ -166,8 +166,18 @@ The `statusCallbackEvent` attribute has the following call status values:
 
 #### Request parameters for the `statusCallback` URL  [#sip_statusCallback]
 
+<llms-ignore>
+
 <WebhookPayloadSnippet webhook="voiceStatusCallback" />
 
+</llms-ignore>
+
+<llms-only>
+
+See the [Voice status callback reference](/docs/compatibility-api/rest/calls/webhooks/voice-status-callback) for the request fields sent to `statusCallback`.
+
+</llms-only>
+
 
 ## Examples
 
diff --git a/fern/products/compatibility-api/pages/rest-api/core/overview.mdx b/fern/products/compatibility-api/pages/rest-api/core/overview.mdx
index f8638d9922..677b7adbb4 100644
--- a/fern/products/compatibility-api/pages/rest-api/core/overview.mdx
+++ b/fern/products/compatibility-api/pages/rest-api/core/overview.mdx
@@ -26,8 +26,18 @@ For developers who prefer working in Postman, we maintain an official Compatibil
 
 Click **Run in Postman** to fork the collection into your own Postman workspace.
 
+<llms-ignore>
+
 [<img src="https://run.pstmn.io/button.svg" alt="Run In Postman" style={{ width: "128px", height: "32px" }} />](https://god.gw.postman.com/run-collection/16445495-16e14ee0-3762-42ac-9f4d-a61401e05209?action=collection%2Ffork&source=rip_markdown&collection-url=entityId%3D16445495-16e14ee0-3762-42ac-9f4d-a61401e05209%26entityType%3Dcollection%26workspaceId%3D4f34e511-485e-4462-a432-20fbc2d1db33)
 
+</llms-ignore>
+
+<llms-only>
+
+[Open the SignalWire Compatibility API collection in Postman](https://god.gw.postman.com/run-collection/16445495-16e14ee0-3762-42ac-9f4d-a61401e05209?action=collection%2Ffork&source=rip_markdown&collection-url=entityId%3D16445495-16e14ee0-3762-42ac-9f4d-a61401e05209%26entityType%3Dcollection%26workspaceId%3D4f34e511-485e-4462-a432-20fbc2d1db33).
+
+</llms-only>
+
 ### Set your credentials
 
 Open the collection's **Variables** tab and fill in the three values from the [API pane](https://my.signalwire.com?page=credentials) of your SignalWire Dashboard:
diff --git a/fern/products/home/pages/welcome.mdx b/fern/products/home/pages/welcome.mdx
index dc10ab0371..49c0930867 100644
--- a/fern/products/home/pages/welcome.mdx
+++ b/fern/products/home/pages/welcome.mdx
@@ -9,6 +9,8 @@ layout: custom
 
 <Markdown src="/snippets/llms-hint.mdx" />
 
+<llms-ignore>
+
 <div class="lp-page-container">
   <div class="main-content">
     {/* Dashed Pattern */}
@@ -114,3 +116,39 @@ layout: custom
 
   </div>
 </div>
+
+</llms-ignore>
+
+<llms-only>
+
+SignalWire is a programmable communications platform for building voice, video, messaging, and AI applications.
+Use the build type or interface below to choose the shortest path into the documentation.
+
+## Choose what to build
+
+| Goal | Start here | Use it for |
+|---|---|---|
+| AI voice agent | [AI application path](/docs/platform/getting-started#ai-application) | LLM-powered phone agents and virtual assistants |
+| Browser or mobile experience | [Browser or mobile path](/docs/platform/getting-started#browser-or-mobile-app) | WebRTC voice, video, and chat in an application |
+| Server application | [Server application path](/docs/platform/getting-started#server-application) | Backend call routing, messaging, interactive voice response, and realtime control |
+| No-code application | [No-code and low-code path](/docs/platform/getting-started#no-code--low-code) | Dashboard AI agents and drag-and-drop call flows |
+| Twilio migration | [Compatibility API](/docs/compatibility-api) | Existing applications that use Twilio-compatible REST APIs or TwiML-compatible markup |
+
+## Choose an interface
+
+| Interface | Start here | Best fit |
+|---|---|---|
+| REST APIs | [REST API documentation](/docs/apis) | Programmatic management of calls, messages, phone numbers, video rooms, and resources |
+| SWML | [SignalWire Markup Language](/docs/swml) | Declarative call and messaging applications returned from webhooks or hosted by SignalWire |
+| Server SDKs | [Server SDK documentation](/docs/server-sdks) | AI agents and realtime call control in a supported programming language |
+| Browser SDK | [Browser SDK documentation](/docs/browser-sdk) | Voice, video, and chat inside browser applications |
+| Call Flow Builder | [Call Flow Builder documentation](/docs/call-flow-builder) | Visual, no-code voice applications |
+| Platform and Dashboard | [Platform documentation](/docs/platform) | Spaces, credentials, phone numbers, resources, and operational configuration |
+| Wirestarter | [Wirestarter documentation](/docs/platform/wirestarter) | Scaffolding a new SignalWire project |
+| SWSH | [SWSH documentation](/docs/platform/swsh) | Interactively testing SWML scripts and API calls |
+
+[Create a SignalWire account](https://signalwire.com/signup), or follow the [Platform getting-started guide](/docs/platform/getting-started) to configure an existing Space.
+
+\*Twilio and TwiML are trademarks of Twilio, Inc. SignalWire, Inc. and its products are not affiliated with or endorsed by Twilio, Inc.
+
+</llms-only>
diff --git a/fern/products/platform/pages/ai/get-started/tool-calling/index.mdx b/fern/products/platform/pages/ai/get-started/tool-calling/index.mdx
index a79dccf89e..8151232d52 100644
--- a/fern/products/platform/pages/ai/get-started/tool-calling/index.mdx
+++ b/fern/products/platform/pages/ai/get-started/tool-calling/index.mdx
@@ -114,8 +114,12 @@ with `"content_type": "text/swaig"`; the fields around those describe the call a
 belongs to. If `web_hook_url` carries credentials in `username:password@host` form, they arrive as
 HTTP basic authentication.
 
+<llms-ignore>
+
 <WebhookPayloadSnippet webhook="aiSwaigToolWebhook" />
 
+</llms-ignore>
+
 The [AI SWAIG tool webhook][swaig-webhook] documents every field, and the
 [`SWAIG.functions` reference][swaig-functions] documents the same fields next to the configuration
 that declares them.
diff --git a/fern/products/platform/pages/getting-started.mdx b/fern/products/platform/pages/getting-started.mdx
index fc1aeececc..adf97ea380 100644
--- a/fern/products/platform/pages/getting-started.mdx
+++ b/fern/products/platform/pages/getting-started.mdx
@@ -29,10 +29,20 @@ In your Dashboard, you can:
 - Access your API credentials
 - Set up AI agents, call flows, and more
 
+<llms-ignore>
+
 <Frame>
   ![The SignalWire Dashboard](/assets/images/dashboard/home/home.webp)
 </Frame>
 
+</llms-ignore>
+
+<llms-only>
+
+The Dashboard's left navigation includes **My Resources**, **Click-to-Call**, **Phone Numbers**, **Messaging Campaigns**, **API Credentials**, **Logs**, **Storage**, and **Configuration**. The home page also displays the current **Project ID** and **Space URL**.
+
+</llms-only>
+
 ## Start building
 
 Let's begin by figuring out the best way for you to build.
@@ -40,6 +50,18 @@ The right approach depends on what you're creating and how you prefer to work.
 
 ### What are you trying to build?
 
+<llms-only>
+
+| What you are building | Primary interface | Choose another interface when |
+|---|---|---|
+| AI voice agent | [Server SDKs](/docs/server-sdks) | Use [SignalWire AI](/docs/platform/ai) for Dashboard configuration or [SWML AI](/docs/swml/reference/calling/ai) when AI is one part of a declarative call flow. |
+| Browser or mobile voice, video, or chat | [Browser SDK](/docs/browser-sdk) | Use a server interface only for trusted backend operations and token issuance. |
+| Backend call or messaging application | [SWML](/docs/swml) | Use the [RELAY client](/docs/server-sdks/guides/relay-client) for persistent realtime control, or Server SDKs for AI agents. |
+| No-code or low-code voice application | [Call Flow Builder](/docs/call-flow-builder) | Use [SWML scripts](/docs/swml) for hosted JSON or YAML, or [SignalWire AI](/docs/platform/ai) for an AI agent. |
+| Existing Twilio application | [Compatibility API](/docs/compatibility-api) | Use SignalWire's native interfaces for AI, which the Compatibility API does not support. |
+
+</llms-only>
+
 <AccordionGroup>
 <Accordion title="AI Application">
 
@@ -52,6 +74,8 @@ This is common for:
 - Lead qualification and surveys
 - Virtual receptionists
 
+<llms-ignore>
+
 <CardGroup cols={3}>
   <Card title="Server SDKs" href="/docs/server-sdks">
     Define agents and host tool handlers in Python or TypeScript application code.
@@ -66,6 +90,8 @@ This is common for:
   </Card>
 </CardGroup>
 
+</llms-ignore>
+
 #### Quick start with the Python Server SDK
 
 ```bash
@@ -136,6 +162,8 @@ Best for applications that need to react to events as they happen.
 They're designed for creating conversational AI that handles phone calls, in the language of your choice:
 the SDK generates the agent configuration and hosts your SWAIG functions for you.
 
+<llms-ignore>
+
 <CardGroup cols={3}>
   <Card title="Server SDKs" href="/docs/server-sdks">
     AI voice agents, any language
@@ -148,6 +176,8 @@ the SDK generates the agent configuration and hosts your SWAIG functions for you
   </Card>
 </CardGroup>
 
+</llms-ignore>
+
 </Accordion>
 <Accordion title="No-Code / Low-Code">
 
@@ -164,6 +194,8 @@ It's not quite "no code" but it's very low code, and you don't need to run any s
 **[Dashboard AI Agents](/docs/platform/resources#in-the-dashboard)** - Configure a conversational AI Agent Resource through your Dashboard. Set up its prompt, choose a voice, and connect it to a phone number.
 The AI handles conversations autonomously.
 
+<llms-ignore>
+
 <CardGroup cols={3}>
   <Card title="Call Flow Builder" href="/docs/call-flow-builder">
     Visual drag-and-drop
@@ -176,6 +208,8 @@ The AI handles conversations autonomously.
   </Card>
 </CardGroup>
 
+</llms-ignore>
+
 #### Quick start for no-code
 
 1. **Buy a phone number** - Go to Phone Numbers in your Dashboard
@@ -201,7 +235,7 @@ In most cases, you can switch by changing a few lines of code.
 | Account SID | Project ID |
 | Auth Token | API Token |
 
-<Warning>
+<Warning title="Compatibility API limitation">
 AI is **not supported** in the Compatibility API.
 Check out the **AI Application** section instead.
 </Warning>
diff --git a/fern/products/platform/pages/messaging/sms/hosted-messaging.mdx b/fern/products/platform/pages/messaging/sms/hosted-messaging.mdx
index 38c1b63989..2e32785dac 100644
--- a/fern/products/platform/pages/messaging/sms/hosted-messaging.mdx
+++ b/fern/products/platform/pages/messaging/sms/hosted-messaging.mdx
@@ -5,10 +5,22 @@ title: Hosted messaging
 description: Learn about porting Messaging services only to the SignalWire platform.
 ---
 
+<llms-ignore>
+
 Hosted Messaging allows you to use SignalWire to send and receive SMS and MMS on 
-<Tooltip tip="10DLC stands for '10-digit long code numbers', such as `(123) 456-7890`. [Learn more](/docs/platform/phone-numbers/getting-started/buying-a-phone-number/#types-of-phone-number)">10DLC</Tooltip> 
+<Tooltip tip="10DLC stands for '10-digit long code numbers', such as `(123) 456-7890`. [Learn more](/docs/platform/phone-numbers)">10DLC</Tooltip>
 and Toll-Free VoIP phone numbers that are held elsewhere for voice (such as a PBX or VoIP provider).
 
+</llms-ignore>
+
+<llms-only>
+
+Hosted Messaging allows you to use SignalWire to send and receive SMS and MMS on
+[10-digit long code (10DLC) phone numbers](/docs/platform/phone-numbers),
+such as `(123) 456-7890`, and Toll-Free VoIP phone numbers that are held elsewhere for voice, such as by a PBX or VoIP provider.
+
+</llms-only>
+
 Use Hosted Messaging to migrate a phone number to SignalWire's robust Messaging platform
 while maintaining your existing Voice infrastructure.
 
diff --git a/fern/products/platform/pages/messaging/whatsapp/receive-messages.mdx b/fern/products/platform/pages/messaging/whatsapp/receive-messages.mdx
index 3b7917d54a..4584e75dbb 100644
--- a/fern/products/platform/pages/messaging/whatsapp/receive-messages.mdx
+++ b/fern/products/platform/pages/messaging/whatsapp/receive-messages.mdx
@@ -37,11 +37,21 @@ You can also view message history graphically in your
 [SignalWire Dashboard](https://my.signalwire.com) under **Logs → Messaging**.
 
 To be notified of each status change as it happens, set `status_callback` when
-[sending a message](/docs/platform/messaging/whatsapp/send-messages). SignalWire then POSTs the
-following payload to your URL at each state change:
+[sending a message](/docs/platform/messaging/whatsapp/send-messages). SignalWire then POSTs a
+message-status payload to your URL at each state change.
+
+<llms-ignore>
 
 <WebhookPayloadSnippet webhook="messageStatusCallback" />
 
+</llms-ignore>
+
+<llms-only>
+
+See the [Message status callback reference](/docs/apis/rest/webhooks/message-status-callback) for every field and status value.
+
+</llms-only>
+
 ## Replying to inbound messages
 
 When a customer messages you first, you can reply with any message type for **24 hours** from their
diff --git a/fern/products/swml/pages/reference/methods/calling/ai/ai_params/index.mdx b/fern/products/swml/pages/reference/methods/calling/ai/ai_params/index.mdx
index 172dbab154..bb62bd0741 100644
--- a/fern/products/swml/pages/reference/methods/calling/ai/ai_params/index.mdx
+++ b/fern/products/swml/pages/reference/methods/calling/ai/ai_params/index.mdx
@@ -629,7 +629,11 @@ event. One moment can produce several: evaluating a
 `input`, `output`, `error_keys`, and `match` together. Handle the properties you recognize and ignore
 the rest, since the set grows over time.
 
+<llms-ignore>
+
 <WebhookPayloadSnippet webhook="aiDebugWebhook" />
 
+</llms-ignore>
+
 See the [AI debug webhook](/docs/apis/rest/webhooks/ai-debug-webhook) webhook page for the full
 field reference.
diff --git a/fern/products/swml/pages/reference/methods/calling/ai/ai_swaig/functions/index.mdx b/fern/products/swml/pages/reference/methods/calling/ai/ai_swaig/functions/index.mdx
index 6cab483165..b37b715366 100644
--- a/fern/products/swml/pages/reference/methods/calling/ai/ai_swaig/functions/index.mdx
+++ b/fern/products/swml/pages/reference/methods/calling/ai/ai_swaig/functions/index.mdx
@@ -112,8 +112,12 @@ object or an array — telling the agent what to do.
 
 <Schema type="Webhooks.AI.AiSwaigToolWebhookPayload" api="signalwire-rest" showDescription />
 
+<llms-ignore>
+
 <WebhookPayloadSnippet webhook="aiSwaigToolWebhook" />
 
+</llms-ignore>
+
 See the [AI SWAIG tool webhook](/docs/apis/rest/webhooks/ai-swaig-tool-webhook) webhook page for the full field reference.
 
 ### Reply
diff --git a/fern/products/swml/pages/reference/methods/calling/ai/ai_swaig/includes/index.mdx b/fern/products/swml/pages/reference/methods/calling/ai/ai_swaig/includes/index.mdx
index 4f9f50a776..4c4432c8fe 100644
--- a/fern/products/swml/pages/reference/methods/calling/ai/ai_swaig/includes/index.mdx
+++ b/fern/products/swml/pages/reference/methods/calling/ai/ai_swaig/includes/index.mdx
@@ -124,8 +124,12 @@ configured—giving your server the context it needs to respond appropriately.
 
 **The discovery request:**
 
+<llms-ignore>
+
 <WebhookPayloadSnippet webhook="swaigSignatureRequest" />
 
+</llms-ignore>
+
 See the [SWAIG function signature request](/docs/apis/rest/webhooks/swaig-signature-request)
 webhook page for the full field reference.
 
diff --git a/fern/products/swml/pages/reference/methods/calling/ai/index.mdx b/fern/products/swml/pages/reference/methods/calling/ai/index.mdx
index f590488f3d..99c57a02a8 100644
--- a/fern/products/swml/pages/reference/methods/calling/ai/index.mdx
+++ b/fern/products/swml/pages/reference/methods/calling/ai/index.mdx
@@ -178,8 +178,12 @@ it is recommended to read the [prompt engineering][prompt-engineering] guide.
 
 SignalWire sends the report to your `post_prompt_url` as an HTTP `POST`.
 
+<llms-ignore>
+
 <WebhookPayloadSnippet webhook="aiPostPromptCallback" />
 
+</llms-ignore>
+
 See the [AI post-prompt callback](/docs/apis/rest/webhooks/ai-post-prompt-callback) webhook
 page for the full field reference.
 
diff --git a/fern/products/swml/pages/reference/methods/calling/ai_sidecar/index.mdx b/fern/products/swml/pages/reference/methods/calling/ai_sidecar/index.mdx
index 33dfa3da7c..e300733bed 100644
--- a/fern/products/swml/pages/reference/methods/calling/ai_sidecar/index.mdx
+++ b/fern/products/swml/pages/reference/methods/calling/ai_sidecar/index.mdx
@@ -205,8 +205,12 @@ Each callback is POSTed to your `url` with the event wrapped under `sidecar_even
 
 The actual event is under `sidecar_event` — unwrap that in your code before reading `type` and the event's fields. Every callback also carries `type`, `ts` (microsecond timestamp), `tick_id`, and a `channel_data` object (`call_id`, plus `caller_id_name` / `caller_id_number` / `destination_number` when available).
 
+<llms-ignore>
+
 <WebhookPayloadSnippet webhook="aiSidecarCallback" />
 
+</llms-ignore>
+
 See the [AI sidecar callback](/docs/apis/rest/webhooks/ai-sidecar-callback) webhook page for the full payload reference. The per-`type` fields are listed below.
 
 ### Callback types
@@ -272,8 +276,12 @@ regular [`ai`](/docs/swml/reference/calling/ai) method's
 [SWAIG webhook](/docs/swml/reference/calling/ai/swaig/functions#tool-webhook), and it groups the
 caller details under `channel_data`.
 
+<llms-ignore>
+
 <WebhookPayloadSnippet webhook="aiSidecarSwaigToolWebhook" />
 
+</llms-ignore>
+
 See the [AI sidecar SWAIG tool webhook](/docs/apis/rest/webhooks/ai-sidecar-swaig-tool-webhook) webhook page for the full field reference.
 
 ### Response
diff --git a/fern/products/swml/pages/reference/methods/calling/bedrock/index.mdx b/fern/products/swml/pages/reference/methods/calling/bedrock/index.mdx
index 3232a95cd9..34c3db66ec 100644
--- a/fern/products/swml/pages/reference/methods/calling/bedrock/index.mdx
+++ b/fern/products/swml/pages/reference/methods/calling/bedrock/index.mdx
@@ -117,8 +117,12 @@ The `post_prompt` object accepts either a plain text prompt or a structured POM
 
 SignalWire sends the report to your `post_prompt_url` as an HTTP `POST`.
 
+<llms-ignore>
+
 <WebhookPayloadSnippet webhook="bedrockPostPromptCallback" />
 
+</llms-ignore>
+
 See the [Amazon Bedrock post-prompt callback](/docs/apis/rest/webhooks/bedrock-post-prompt-callback)
 webhook page for the full field reference.
 
diff --git a/fern/products/swml/pages/reference/methods/calling/bedrock/swaig/functions/index.mdx b/fern/products/swml/pages/reference/methods/calling/bedrock/swaig/functions/index.mdx
index b58c6e11e3..2028afc2f5 100644
--- a/fern/products/swml/pages/reference/methods/calling/bedrock/swaig/functions/index.mdx
+++ b/fern/products/swml/pages/reference/methods/calling/bedrock/swaig/functions/index.mdx
@@ -85,8 +85,12 @@ is `text/json` rather than `text/swaig`, `argument` carries no `substituted` val
 Write your handler against this list, not the `ai` one.
 </Note>
 
+<llms-ignore>
+
 <WebhookPayloadSnippet webhook="bedrockSwaigToolWebhook" />
 
+</llms-ignore>
+
 See the [Amazon Bedrock SWAIG tool webhook](/docs/apis/rest/webhooks/bedrock-swaig-tool-webhook)
 webhook page for the full field reference.
 
diff --git a/fern/products/swml/pages/reference/methods/calling/overview.mdx b/fern/products/swml/pages/reference/methods/calling/overview.mdx
index 53cc4d6879..a23812a3d0 100644
--- a/fern/products/swml/pages/reference/methods/calling/overview.mdx
+++ b/fern/products/swml/pages/reference/methods/calling/overview.mdx
@@ -68,8 +68,18 @@ the script runs, methods also populate the **`vars.*` runtime scope** — those
 the initial inbound payload, but they are propagated across `transfer` boundaries and delivered
 on subsequent fetches.
 
+<llms-ignore>
+
 <WebhookPayloadSnippet webhook="inboundCallWebhook" />
 
+</llms-ignore>
+
+<llms-only>
+
+See the [SWML inbound call webhook reference](/docs/apis/rest/webhooks/inbound-call-webhook) for the complete request schema. The fields used by SWML are documented below.
+
+</llms-only>
+
 <ParamField path="call" type="object" toc={true}>
   Information about the current call. Call-specific and read-only. Each call leg (A-leg, B-leg)
   has its own unique `call` object with different `call_id`, `from`, `to`, etc. When connecting
diff --git a/fern/products/swml/pages/reference/methods/calling/send_sms.mdx b/fern/products/swml/pages/reference/methods/calling/send_sms.mdx
index fab13cfa82..cc0f38cde0 100644
--- a/fern/products/swml/pages/reference/methods/calling/send_sms.mdx
+++ b/fern/products/swml/pages/reference/methods/calling/send_sms.mdx
@@ -106,10 +106,14 @@ When `status_callback` is set, SignalWire sends an HTTP `POST` to that URL each
 message transitions to a new state. Callback delivery is independent of SWML execution: the document
 continues as soon as the message is accepted, and delivery-state callbacks fire afterwards.
 
-The callback uses the same payload as other outbound messages sent through SignalWire:
+The callback uses the same payload as other outbound messages sent through SignalWire.
+
+<llms-ignore>
 
 <WebhookPayloadSnippet webhook="messageStatusCallback" />
 
+</llms-ignore>
+
 See the [Message status callback](/docs/apis/rest/webhooks/message-status-callback)
 webhook page for the full field reference and the list of possible `status` values.
 
diff --git a/fern/products/swml/pages/reference/methods/calling/stream.mdx b/fern/products/swml/pages/reference/methods/calling/stream.mdx
index 8d9f3c820e..239d8f3928 100644
--- a/fern/products/swml/pages/reference/methods/calling/stream.mdx
+++ b/fern/products/swml/pages/reference/methods/calling/stream.mdx
@@ -83,8 +83,12 @@ The stream keeps running until you stop it with [`stop_stream`](/docs/swml/refer
 
 When you set `status_url`, SignalWire POSTs a `calling.call.stream` event to it whenever the stream changes state: `params.state` is `streaming` when the stream starts and `finished` when it ends.
 
+<llms-ignore>
+
 <WebhookPayloadSnippet webhook="streamStatusCallback" />
 
+</llms-ignore>
+
 See the [Stream status callback](/docs/apis/rest/webhooks/stream-status-callback) webhook page for the full field reference.
 
 ---
diff --git a/fern/products/swml/pages/reference/methods/calling/transcribe.mdx b/fern/products/swml/pages/reference/methods/calling/transcribe.mdx
index ef0e0ed9f4..c7028744b5 100644
--- a/fern/products/swml/pages/reference/methods/calling/transcribe.mdx
+++ b/fern/products/swml/pages/reference/methods/calling/transcribe.mdx
@@ -45,8 +45,12 @@ Only one transcription can be active on a call at a time. Starting another while
 
 When you set `status_url`, SignalWire POSTs a transcript event to it when the call's transcription finishes: `calling.transcript.completed` includes the transcribed `text` when speech was captured, or `calling.transcript.failed` if the call could not be transcribed.
 
+<llms-ignore>
+
 <WebhookPayloadSnippet webhook="transcribeStatusCallback" />
 
+</llms-ignore>
+
 See the [Transcript status callback](/docs/apis/rest/webhooks/transcribe-status-callback) webhook page for the full field reference.
 
 ---
diff --git a/fern/products/swml/pages/reference/methods/messaging/overview.mdx b/fern/products/swml/pages/reference/methods/messaging/overview.mdx
index fbeaad353f..706d3a12e2 100644
--- a/fern/products/swml/pages/reference/methods/messaging/overview.mdx
+++ b/fern/products/swml/pages/reference/methods/messaging/overview.mdx
@@ -36,8 +36,18 @@ variable expansion (for example, `%{message.from}`). As the script runs, methods
 the **`vars.*` runtime scope** — those values are not in the initial inbound payload, but they
 are propagated across `transfer` boundaries and delivered on transfer-driven fetches.
 
+<llms-ignore>
+
 <WebhookPayloadSnippet webhook="inboundMessageWebhook" />
 
+</llms-ignore>
+
+<llms-only>
+
+See the [SWML inbound message webhook reference](/docs/apis/rest/webhooks/inbound-message-webhook) for the complete request schema. The fields used by SWML are documented below.
+
+</llms-only>
+
 <ParamField path="message" type="object" toc={true}>
   The inbound message that triggered the SWML document.
 </ParamField>
@@ -213,4 +223,3 @@ systems know.
     Call an external API while handling the message — for example, to look up a customer record before replying.
   </Card>
 </CardGroup>
-
diff --git a/fern/products/swml/pages/reference/methods/messaging/reply.mdx b/fern/products/swml/pages/reference/methods/messaging/reply.mdx
index 117e111a60..c9bbfe5379 100644
--- a/fern/products/swml/pages/reference/methods/messaging/reply.mdx
+++ b/fern/products/swml/pages/reference/methods/messaging/reply.mdx
@@ -147,10 +147,14 @@ callback on any other outbound message sent through SignalWire.
 
 When `status_url` is set, SignalWire sends an HTTP `POST` to that URL each time the outbound reply
 transitions to a new state. The callback uses the same payload as other outbound messages sent
-through SignalWire:
+through SignalWire.
+
+<llms-ignore>
 
 <WebhookPayloadSnippet webhook="messageStatusCallback" />
 
+</llms-ignore>
+
 See the [Message status callback](/docs/apis/rest/webhooks/message-status-callback)
 webhook page for the full field reference and the list of possible `status` values.
 
@@ -401,4 +405,3 @@ sections:
 ```
 </CodeBlock>
 </CodeBlocks>
-
diff --git a/fern/products/swml/pages/reference/methods/messaging/transfer.mdx b/fern/products/swml/pages/reference/methods/messaging/transfer.mdx
index 3aac161823..abe79b2f8f 100644
--- a/fern/products/swml/pages/reference/methods/messaging/transfer.mdx
+++ b/fern/products/swml/pages/reference/methods/messaging/transfer.mdx
@@ -51,8 +51,18 @@ to `dest`:
   `reply_result`, `request_response`, `request_response_code`, `request_response_body`,
   `reply_message_id`). Present on transfer-driven fetches; absent on the initial inbound fetch.
 
+<llms-ignore>
+
 <WebhookPayloadSnippet webhook="inboundMessageWebhook" />
 
+</llms-ignore>
+
+<llms-only>
+
+See the [SWML inbound message webhook reference](/docs/apis/rest/webhooks/inbound-message-webhook) for the complete request schema.
+
+</llms-only>
+
 ## **Examples**
 
 ### Transfer to an external SWML handler
@@ -165,4 +175,3 @@ sections:
 </CodeBlock>
 </CodeBlocks>
 
-
diff --git a/package.json b/package.json
index 5cd58f8361..3190e4524f 100644
--- a/package.json
+++ b/package.json
@@ -19,6 +19,7 @@
     "fern-md-check": "fern docs md check",
     "check-links": "node scripts/check-links.js",
     "check-md-exports": "node scripts/check-md-exports.js",
+    "check-llm-exports": "node scripts/check-llm-exports.mjs",
     "test:scripts": "node --test \"scripts/**/*.test.js\"",
     "format:specs": "yarn workspace signalwire-docs-specs format",
     "format:specs:check": "yarn workspace signalwire-docs-specs format:check",
diff --git a/scripts/README.md b/scripts/README.md
index 77e769337f..7a882c2b6e 100644
--- a/scripts/README.md
+++ b/scripts/README.md
@@ -10,6 +10,9 @@ dependencies beyond what's in `package.json`) and share conventions: hand-rolled
 | `check-links.js` | `yarn check-links` | Validate every link on the published site (lychee over the sitemap, plus local git-based verification of GitHub blob/tree/tag URLs). |
 | `check-md-exports.js` | `yarn check-md-exports` | Audit the `.md` exports and `llms.txt` indexes served for AI consumption. |
 | `check-md-exports.test.js` | `yarn test:scripts` | Fixture tests locking in `check-md-exports.js`'s detection heuristics. |
+| `check-llm-exports.mjs` | `yarn check-llm-exports <preview-url>` | Check issue-specific required and forbidden content in preview `.md` exports. |
+| `llm-export-cases.json` | Used by `check-llm-exports.mjs` | Manifest of routes and semantic export assertions. |
+| `llm-agent-scenarios.md` | Manual preview evaluation | Context-isolated agent prompts and expected documentation destinations. |
 | `postman/` | `yarn postman:build` / `postman:publish` | Build and publish the Postman collection from the OpenAPI specs. |
 | `utils/logger.js` | — | Shared leveled logger (text/JSON, collectors) used by the scripts above. |
 
diff --git a/scripts/check-llm-exports.mjs b/scripts/check-llm-exports.mjs
new file mode 100644
index 0000000000..45d1a66068
--- /dev/null
+++ b/scripts/check-llm-exports.mjs
@@ -0,0 +1,106 @@
+#!/usr/bin/env node
+
+import { readFile } from 'node:fs/promises';
+import { dirname, join } from 'node:path';
+import { fileURLToPath } from 'node:url';
+
+const SCRIPT_DIR = dirname(fileURLToPath(import.meta.url));
+const DEFAULT_MANIFEST = join(SCRIPT_DIR, 'llm-export-cases.json');
+const MAX_ATTEMPTS = 5;
+
+function normalizeDocsBase(rawBaseUrl) {
+  const url = new URL(rawBaseUrl);
+  url.hash = '';
+  url.search = '';
+  url.pathname = url.pathname.replace(/\/+$/, '');
+  if (!url.pathname.endsWith('/docs')) url.pathname = `${url.pathname || ''}/docs`.replace(/\/{2,}/g, '/');
+  return url.toString().replace(/\/$/, '');
+}
+
+function checkBody(testCase, body) {
+  const failures = [];
+
+  if (/(?:^|\n)# Page Not Found(?:\n|$)/.test(body)) {
+    failures.push('received a Page Not Found stub');
+  }
+
+  if (body.includes('X-Amz-Signature')) {
+    failures.push('contains a presigned image URL');
+  }
+
+  for (const required of testCase.contains ?? []) {
+    if (!body.includes(required)) failures.push(`missing required text: ${JSON.stringify(required)}`);
+  }
+
+  for (const forbidden of testCase.notContains ?? []) {
+    if (body.includes(forbidden)) failures.push(`contains forbidden text: ${JSON.stringify(forbidden)}`);
+  }
+
+  return failures;
+}
+
+async function fetchWithRetry(url) {
+  let lastError;
+
+  for (let attempt = 1; attempt <= MAX_ATTEMPTS; attempt++) {
+    try {
+      const response = await fetch(url, {
+        headers: { 'User-Agent': 'signalwire-docs-llm-export-check' },
+        signal: AbortSignal.timeout(30_000),
+      });
+
+      if (response.ok) return response.text();
+      lastError = new Error(`HTTP ${response.status}`);
+      if (response.status < 500 && response.status !== 429) break;
+    } catch (error) {
+      lastError = error;
+    }
+
+    if (attempt < MAX_ATTEMPTS) {
+      await new Promise((resolve) => setTimeout(resolve, 2 ** attempt * 1_000));
+    }
+  }
+
+  throw lastError;
+}
+
+async function main() {
+  const [rawBaseUrl, manifestPath = DEFAULT_MANIFEST] = process.argv.slice(2);
+  if (!rawBaseUrl) {
+    console.error('Usage: node scripts/check-llm-exports.mjs <preview-base-url> [manifest]');
+    process.exit(2);
+  }
+
+  const baseUrl = normalizeDocsBase(rawBaseUrl);
+  const testCases = JSON.parse(await readFile(manifestPath, 'utf8'));
+  const failures = [];
+
+  await Promise.all(testCases.map(async (testCase) => {
+    const url = `${baseUrl}${testCase.path}`;
+    try {
+      const body = await fetchWithRetry(url);
+      for (const failure of checkBody(testCase, body)) {
+        failures.push(`${testCase.name} (${url}): ${failure}`);
+      }
+    } catch (error) {
+      failures.push(`${testCase.name} (${url}): ${error.message}`);
+    }
+  }));
+
+  if (failures.length > 0) {
+    console.error(`LLM export checks failed (${failures.length}):`);
+    for (const failure of failures) console.error(`- ${failure}`);
+    process.exit(1);
+  }
+
+  console.log(`LLM export checks passed for ${testCases.length} routes.`);
+}
+
+export { checkBody, normalizeDocsBase };
+
+if (process.argv[1] === fileURLToPath(import.meta.url)) {
+  main().catch((error) => {
+    console.error(error.stack ?? error.message);
+    process.exit(2);
+  });
+}
diff --git a/scripts/check-llm-exports.test.js b/scripts/check-llm-exports.test.js
new file mode 100644
index 0000000000..f4d2e4269c
--- /dev/null
+++ b/scripts/check-llm-exports.test.js
@@ -0,0 +1,35 @@
+import assert from 'node:assert/strict';
+import test from 'node:test';
+
+import { checkBody, normalizeDocsBase } from './check-llm-exports.mjs';
+
+test('normalizes Fern preview URLs to the docs base', () => {
+  assert.equal(normalizeDocsBase('https://example.docs.buildwithfern.com'), 'https://example.docs.buildwithfern.com/docs');
+  assert.equal(normalizeDocsBase('https://example.docs.buildwithfern.com/docs/'), 'https://example.docs.buildwithfern.com/docs');
+});
+
+test('reports missing and forbidden export content', () => {
+  const failures = checkBody({
+    contains: ['orientation', 'functional link'],
+    notContains: ['class="fern-page-heading"'],
+  }, 'orientation\nclass="fern-page-heading"');
+
+  assert.deepEqual(failures, [
+    'missing required text: "functional link"',
+    'contains forbidden text: "class=\\"fern-page-heading\\""',
+  ]);
+});
+
+test('reports Fern soft-404 bodies even for notContains-only cases', () => {
+  const failures = checkBody({
+    notContains: ['<VoiceWidget'],
+  }, '> Documentation index\n\n# Page Not Found\n');
+
+  assert.deepEqual(failures, ['received a Page Not Found stub']);
+});
+
+test('reports presigned image URLs', () => {
+  const failures = checkBody({}, 'https://example.com/image.webp?X-Amz-Signature=temporary');
+
+  assert.deepEqual(failures, ['contains a presigned image URL']);
+});
diff --git a/scripts/llm-agent-scenarios.md b/scripts/llm-agent-scenarios.md
new file mode 100644
index 0000000000..bbd75f663f
--- /dev/null
+++ b/scripts/llm-agent-scenarios.md
@@ -0,0 +1,14 @@
+# LLM documentation scenarios
+
+Run each prompt in a new, context-isolated agent session against the Fern preview. Record the selected product, canonical documentation link, supporting text, and pass/fail result in the final rollout PR.
+
+| Scenario | Prompt | Expected result |
+|---|---|---|
+| Python phone agent | “I need to build an AI phone agent in Python that can call my scheduling backend. Where do I start?” | Server SDKs and the Python quickstart; tool calling for backend actions. |
+| Mid-call transfer | “My server must decide during an active call whether to transfer the caller. Should I use SWML or RELAY?” | RELAY for imperative realtime control; SWML for declarative call instructions. |
+| Browser credentials | “What credential can I safely give a browser click-to-call app?” | A browser/embed token, not a Project API token. |
+| Purchase a number | “How can my backend search for and purchase a SignalWire phone number?” | REST phone-number search and purchase endpoints. |
+| Provider voice | “How do I configure a Speechify or Cartesia voice for text-to-speech?” | The provider page, required voice identifier format, and provider voice-list link. |
+| WhatsApp callback | “What JSON will my WhatsApp message status callback receive?” | The Message status callback payload and canonical webhook reference. |
+| No-code call handling | “I need a phone menu without running a server or writing code.” | Call Flow Builder. |
+| Twilio migration | “Can I move my Twilio application to SignalWire and keep its AI features?” | Compatibility API for compatible REST/cXML behavior and an explicit warning that AI is unsupported there. |
diff --git a/scripts/llm-export-cases.json b/scripts/llm-export-cases.json
new file mode 100644
index 0000000000..36feab3cd1
--- /dev/null
+++ b/scripts/llm-export-cases.json
@@ -0,0 +1,138 @@
+[
+  {
+    "name": "Documentation homepage",
+    "path": ".md",
+    "contains": [
+      "SignalWire is a programmable communications platform",
+      "## Choose what to build",
+      "[Platform getting-started guide](/docs/platform/getting-started)",
+      "Twilio and TwiML are trademarks"
+    ],
+    "notContains": [
+      "class=\"fern-page-heading",
+      "<Button",
+      "<div class=\"lp-page-container"
+    ]
+  },
+  {
+    "name": "Root llms.txt orientation",
+    "path": "/llms.txt",
+    "contains": [
+      "SignalWire is a programmable communications platform",
+      "## Choose what to build"
+    ],
+    "notContains": [
+      "class=\"fern-page-heading",
+      "<div class=\"lp-page-container"
+    ]
+  },
+  {
+    "name": "Platform getting started",
+    "path": "/platform/getting-started.md",
+    "contains": [
+      "| What you are building",
+      "| Primary interface",
+      "The Dashboard's left navigation includes",
+      "#### Quick start with the Python Server SDK",
+      "Compatibility API limitation"
+    ],
+    "notContains": [
+      "/assets/images/dashboard/home/home.webp"
+    ]
+  },
+  {
+    "name": "WhatsApp message status callback",
+    "path": "/platform/messaging/whatsapp/receive-messages.md",
+    "contains": [
+      "[Message status callback reference](/docs/apis/rest/webhooks/message-status-callback)"
+    ],
+    "notContains": [
+      "<WebhookPayloadSnippet"
+    ]
+  },
+  {
+    "name": "Hosted messaging tooltip definition",
+    "path": "/platform/messaging/hosted-messaging.md",
+    "contains": [
+      "10-digit long code (10DLC) phone numbers"
+    ],
+    "notContains": [
+      "<Tooltip"
+    ]
+  },
+  {
+    "name": "AI overview diagram fallback",
+    "path": "/platform/ai.md",
+    "contains": [
+      "flowchart LR",
+      "Voice[\"Voice<br />PSTN · SIP · WebRTC\"]",
+      "Your backend — the only network hop off platform"
+    ],
+    "notContains": [
+      "ai-agent-flow-themed.svg"
+    ]
+  },
+  {
+    "name": "Prompt engineering surfaces",
+    "path": "/platform/ai/prompt-engineering.md",
+    "contains": [
+      "## Prompt surfaces",
+      "| Prompt surface",
+      "A prompt requests behavior; code enforces it."
+    ],
+    "notContains": [
+      "<Tooltip"
+    ]
+  },
+  {
+    "name": "Call Flow Builder demo",
+    "path": "/call-flow-builder.md",
+    "contains": [
+      "[Call Flow Builder demonstration](https://www.youtube.com/watch?v=ZPnwEKOhYH4)"
+    ],
+    "notContains": [
+      "<iframe"
+    ]
+  },
+  {
+    "name": "REST API Postman collection",
+    "path": "/apis.md",
+    "contains": [
+      "[Open the SignalWire REST API collection in Postman]"
+    ],
+    "notContains": [
+      "run.pstmn.io/button.svg"
+    ]
+  },
+  {
+    "name": "Compatibility API Postman collection",
+    "path": "/compatibility-api/rest.md",
+    "contains": [
+      "[Open the SignalWire Compatibility API collection in Postman]"
+    ],
+    "notContains": [
+      "run.pstmn.io/button.svg"
+    ]
+  },
+  {
+    "name": "Compatibility voice callback reference",
+    "path": "/compatibility-api/cxml/reference/voice/sip.md",
+    "contains": [
+      "[Voice status callback reference](/docs/compatibility-api/rest/calls/webhooks/voice-status-callback)"
+    ],
+    "notContains": [
+      "<WebhookPayloadSnippet"
+    ]
+  },
+  {
+    "name": "Compatibility recording callbacks",
+    "path": "/compatibility-api/cxml/reference/voice/record.md",
+    "contains": [
+      "[Recording status callback reference](/docs/compatibility-api/rest/recordings/webhooks/recording-status-callback)",
+      "[Transcription status callback reference](/docs/compatibility-api/rest/recording-transcriptions/webhooks/transcription-status-callback)"
+    ],
+    "notContains": [
+      "<WebhookPayloadSnippet"
+    ]
+  }
+]