@assistant-ui/mcp-docs-server 0.1.36 → 0.1.39

package/.docs/raw/docs/(reference)/api-reference/generative-ui/actions.mdx

@@ -0,0 +1,56 @@
+---
+title: Generative UI Actions
+description: "Register handlers for model-emitted $action payloads and dispatch them from interactive generative UI components."
+---
+
+import { ActionDispatchContext, ActionRegistry, createActionRegistry } from "@/generated/typeDocs";
+
+{/* AUTO-GENERATED PAGE by scripts/generate-api-reference.mts */}
+{/* Do not edit manually. */}
+
+{/* api-reference:start */}
+{/* AUTO-GENERATED by scripts/generate-api-reference.mts */}
+{/* Do not edit this block manually. */}
+
+## API Reference
+
+### ActionDispatchContext
+
+Context handed to an [ActionHandler](/docs/api-reference/generative-ui/actions#actionhandler) when an `$action` fires.
+
+<ParametersTable {...ActionDispatchContext} />
+
+### ActionHandler
+
+Resolves a single `$action.type`. Fire-and-forget actions return `void` or a
+promise that resolves to it; human-in-the-loop actions return a value the
+runtime uses to resume the run (see IR doc Open question #2 — the resume
+value is left as `unknown` and documented per-action). The return value is
+handed back to `dispatch`'s caller as `unknown`.
+
+```ts
+type ActionHandler = (
+  ctx: ActionDispatchContext,
+) => unknown | Promise<unknown>;
+```
+
+### ActionRegistry
+
+The host-provided map from `$action.type` to [ActionHandler](/docs/api-reference/generative-ui/actions#actionhandler). This is the single dispatch target for rendered generative UI: every interactive component fires its `$action` here through the injected `$dispatch` (a submit Button defers to its ancestor form's dispatch instead). The payload's `$input` takes one of two shapes: a single value for a standalone control's dispatch (`Select`, `Input`, `DatePicker`, `Checkbox`, `RadioGroup`), or an object keyed by field `name` for a `Form` or a `Card` with `asForm` set. Construct it with [createActionRegistry](/docs/api-reference/generative-ui/actions#createactionregistry) and pass it to `JSONGenerativeUI`.
+
+<ParametersTable {...ActionRegistry} />
+
+### createActionRegistry
+
+<ParametersTable {...createActionRegistry} />
+
+### emptyActionRegistry
+
+A no-op registry used when no handlers are provided. Dispatch resolves to
+`undefined` and logs a warning in dev for unknown types, so a model-emitted
+action with no handler degrades to "does nothing" rather than throwing.
+
+```ts
+const emptyActionRegistry: ActionRegistry;
+```
+{/* api-reference:end */}

package/.docs/raw/docs/(reference)/api-reference/generative-ui/components.mdx

@@ -0,0 +1,86 @@
+---
+title: Generative UI Components
+description: Define the component library JSONGenerativeUI can render, including schemas, render functions, and the default vocabulary.
+---
+
+import { GenerativeUIComponent, defineGenerativeComponents } from "@/generated/typeDocs";
+
+{/* AUTO-GENERATED PAGE by scripts/generate-api-reference.mts */}
+{/* Do not edit manually. */}
+
+{/* api-reference:start */}
+{/* AUTO-GENERATED by scripts/generate-api-reference.mts */}
+{/* Do not edit this block manually. */}
+
+## API Reference
+
+### defaultGenerativeUILibrary
+
+The closed generative-ui vocabulary the factory ships: a fixed set of
+intrinsic components the model may render, each a zod `properties` schema
+plus an unstyled structural `render` (semantic HTML with a `data-aui`
+attribute naming the component, plus `data-aui-<prop>` hooks, for the host
+to style). Users opt in by passing it to
+`new JSONGenerativeUI({ library: defaultGenerativeUILibrary })`, and override
+or extend entries with their own `defineGenerativeComponents`.
+
+```ts
+const defaultGenerativeUILibrary: GenerativeUILibrary;
+```
+
+### defineGenerativeComponents
+
+Authoring helper for a `"use generative"` generative-UI library — the set of
+components the model may render. Each component colocates its `properties`
+schema (kept on every build, drives the tool parameters) with its `render`
+(kept only on the client). Pass the result to [JSONGenerativeUI](/docs/api-reference/generative-ui/json-generative-ui#jsongenerativeui):
+
+```tsx
+"use generative";
+const generative = new JSONGenerativeUI({
+  library: defineGenerativeComponents({
+    Card: {
+      description: "A card.",
+      properties: z.object({ title: z.string() }),
+      render: (props) => <Card {...props} />,
+    },
+  }),
+});
+```
+
+Unlike [defineToolkit](/docs/api-reference/tools/toolkits#definetoolkit), it has **no runtime implementation**. A
+`"use generative"` compiler unwraps the `defineGenerativeComponents(...)` call
+per build, dropping each `render` (and its client-only imports) from the server
+build. Reaching it at runtime means the module wasn't compiled (the directive
+is missing, or it was used outside a `"use generative"` file), so it throws
+rather than shipping client `render` code to the server.
+
+<ParametersTable {...defineGenerativeComponents} />
+
+### GenerativeUIComponent
+
+A component the model is allowed to render, with the schema for its props.
+
+Components opt into prop streaming with `streamProperties`: they render as
+props arrive, so `render` sees `Partial<P>` while `$status` is `"streaming"`
+and the full `P` once it is `"done"`. By default a component opts out and is
+only rendered once its props are complete.
+
+`render` is a function of `props`, not a React component. Direct hook use is
+fine (each node is mounted on its own fiber), but a given node must keep its
+`type` across renders for hook identity to be stable.
+
+<ParametersTable {...GenerativeUIComponent} />
+
+### GenerativeUILibrary
+
+The consumer-provided allowlist of components the model is permitted to
+render. Keys are the `type` values referenced in the generative-ui tree
+(e.g. `"Card"`, `"Button"`); values describe each component.
+
+This registry is the security boundary — any `type` not present is rejected.
+
+```ts
+type GenerativeUILibrary = Record<string, GenerativeUIComponent>;
+```
+{/* api-reference:end */}

package/.docs/raw/docs/(reference)/api-reference/generative-ui/index.mdx

@@ -9,10 +9,28 @@ description: Spec-driven generative UI for assistant-ui. The data format an assi
 ## Pages
 
 <Cards>
+  <Card title={"JSONGenerativeUI"} href={"/docs/api-reference/generative-ui/json-generative-ui"}>
+    {"Create present and prompt_user tools from a generative UI component library, with options for display mode and action dispatch."}
+  </Card>
+  <Card title={"Generative UI Components"} href={"/docs/api-reference/generative-ui/components"}>
+    {"Define the component library JSONGenerativeUI can render, including schemas, render functions, and the default vocabulary."}
+  </Card>
+  <Card title={"Generative UI Actions"} href={"/docs/api-reference/generative-ui/actions"}>
+    {"Register handlers for model-emitted $action payloads and dispatch them from interactive generative UI components."}
+  </Card>
   <Card title={"Generative UI Spec"} href={"/docs/api-reference/generative-ui/spec"}>
     {"The serializable node tree an assistant emits to describe generative UI. Covers the GenerativeUISpec format, its nodes, and the message part that carries the spec."}
   </Card>
   <Card title={"Generative UI Rendering"} href={"/docs/api-reference/generative-ui/rendering"}>
-    {"Render a generative UI spec into React. The renderer resolves spec nodes against your component registry, and the error thrown when a component cannot be resolved."}
+    {"Render generative UI trees, build present-tool schemas, and inspect or serialize model-produced UI nodes."}
+  </Card>
+  <Card title={"Slack Block Kit"} href={"/docs/api-reference/generative-ui/slack"}>
+    {"Convert generative UI trees to Slack Block Kit payloads and decode block_actions interactions back into $action payloads."}
+  </Card>
+  <Card title={"Microsoft Teams"} href={"/docs/api-reference/generative-ui/teams"}>
+    {"Convert generative UI trees to Teams Adaptive Cards and decode Action.Submit payloads back into $action payloads."}
+  </Card>
+  <Card title={"Generative UI Tokens"} href={"/docs/api-reference/generative-ui/tokens"}>
+    {"Shared token arrays used by the default generative UI vocabulary for sizing, color, alignment, and component variants."}
   </Card>
 </Cards>

package/.docs/raw/docs/(reference)/api-reference/generative-ui/json-generative-ui.mdx

@@ -0,0 +1,42 @@
+---
+title: JSONGenerativeUI
+description: "Create present and prompt_user tools from a generative UI component library, with options for display mode and action dispatch."
+---
+
+import { JSONGenerativeUI, JSONGenerativeUIOptions, PresentToolOptions } from "@/generated/typeDocs";
+
+{/* AUTO-GENERATED PAGE by scripts/generate-api-reference.mts */}
+{/* Do not edit manually. */}
+
+{/* api-reference:start */}
+{/* AUTO-GENERATED by scripts/generate-api-reference.mts */}
+{/* Do not edit this block manually. */}
+
+## API Reference
+
+### JSONGenerativeUI
+
+Client build of [JSONGenerativeUI](/docs/api-reference/generative-ui/json-generative-ui#jsongenerativeui), resolved through the package's
+`default` export condition (browser and SSR).
+
+`present` is a frontend tool that renders the model's `{ $type,...props }`
+tree against the library and resolves immediately. `prompt_user` is a
+human-in-the-loop tool: the model pauses and the rendered UI supplies the
+result. Both draw the tree the same way, so they share one `render`. The
+`actions` registry (if provided) is threaded into the render context so
+interactive components can fire `$action` through `$dispatch`.
+
+<ParametersTable {...JSONGenerativeUI} />
+
+### JSONGenerativeUIOptions
+
+Options for [JSONGenerativeUI](/docs/api-reference/generative-ui/json-generative-ui#jsongenerativeui).
+
+<ParametersTable {...JSONGenerativeUIOptions} />
+
+### PresentToolOptions
+
+Options for [JSONGenerativeUI.present](/docs/api-reference/generative-ui/json-generative-ui#jsongenerativeui).
+
+<ParametersTable {...PresentToolOptions} />
+{/* api-reference:end */}

package/.docs/raw/docs/(reference)/api-reference/generative-ui/rendering.mdx

@@ -1,9 +1,9 @@
 ---
 title: Generative UI Rendering
-description: Render a generative UI spec into React. The renderer resolves spec nodes against your component registry, and the error thrown when a component cannot be resolved.
+description: Render generative UI trees, build present-tool schemas, and inspect or serialize model-produced UI nodes.
 ---
 
-import { GenerativeUIRender, GenerativeUIRenderError } from "@/generated/typeDocs";
+import { GenerativeUIRender, GenerativeUIRenderContext, GenerativeUIRenderError, buildPresentParameters, generativeUIToJSX, renderGenerativeUI } from "@/generated/typeDocs";
 
 {/* AUTO-GENERATED PAGE by scripts/generate-api-reference.mts */}
 {/* Do not edit manually. */}
@@ -14,6 +14,26 @@ import { GenerativeUIRender, GenerativeUIRenderError } from "@/generated/typeDoc
 
 ## API Reference
 
+### buildPresentParameters
+
+Builds the JSON schema for the `present` tool from a [GenerativeUILibrary](/docs/api-reference/generative-ui/components#generativeuilibrary).
+
+The model produces a node `{ $type, $key?,...props }` where `$type` selects
+a component, the optional `$key` pins a stable identity for list items that
+may reorder, and the rest are its props. The schema is a flat object: `$type`
+is an enum of the component names, every component's props are merged into
+one optional bag, and `children` recurses via `$defs` so the tree can nest.
+
+It is intentionally flat rather than a per-`$type` discriminated union. Tool /
+function-call schemas (OpenAI and others) require the top-level parameters to
+be a plain object and reject a top-level `oneOf`/`anyOf`/`enum`. So props can't
+be refined per `$type` at the root; the model is guided instead by `$type`'s
+description (which lists each component) and each prop's own description. The
+renderer validates nothing here — an unknown `$type` or stray prop is handled
+at render time — so a looser schema only costs the model a hint, not safety.
+
+<ParametersTable {...buildPresentParameters} />
+
 ### GenerativeUIRender
 
 Internal renderer. Resolves a [GenerativeUISpec](/docs/api-reference/generative-ui/spec#generativeuispec) against the consumer
@@ -22,6 +42,12 @@ allowlist. Used by `MessagePrimitive.GenerativeUI` and by
 
 <ParametersTable {...GenerativeUIRender} />
 
+### GenerativeUIRenderContext
+
+The render context threaded through [renderGenerativeUI](/docs/api-reference/generative-ui/rendering#rendergenerativeui).
+
+<ParametersTable {...GenerativeUIRenderContext} />
+
 ### GenerativeUIRenderError
 
 Thrown when a generative-ui spec references a component name that is not
@@ -30,4 +56,29 @@ boundary in the same-realm rendering path — there is no fallback by
 default. Pass `Fallback` to opt into a soft-fail UX.
 
 <ParametersTable {...GenerativeUIRenderError} />
+
+### generativeUIToJSX
+
+Serializes a generative-UI node to a JSX-like string for display: the "view source" of a model-produced tree. The wire form `{ $type: "Weather", id: "x" }` becomes `<Weather id="x" />`, and nested `children` render between tags: `<Card title="Hi"><Text>hello</Text></Card>`. A model-provided `$key` becomes the JSX `key` attribute.
+
+By default this is a faithful textual rendering, not a parser: text children are emitted verbatim (not HTML/JSX-escaped), so the result is meant to be shown, not re-parsed. Returns `""` for nodes that aren't renderable (no `$type` yet, `null`, booleans).
+
+Pass `{ escape: true }` to make the output safe to paste back into JSX: any string child containing `<`, `>`, `&`, `{`, or `}` is emitted as a JSON-stringified expression (`{JSON.stringify(child)}`) instead of verbatim, while a string child with none of those characters still renders verbatim.
+
+Pass `{ pretty: true }` to pretty-print nested element trees with two-space indentation, while pure text children stay on one line.
+
+<ParametersTable {...generativeUIToJSX} />
+
+### renderGenerativeUI
+
+Renders a generative-ui tree against a [GenerativeUILibrary](/docs/api-reference/generative-ui/components#generativeuilibrary).
+
+The model emits each node as a flat object `{ $type,...props }`. We first
+normalize that wire form into the canonical NormalizedUINode (with
+`children` lifted to a reserved top-level key), then render: each `type` is
+looked up in the library and its `props` are passed to the component's
+`render(props, context)`, with `children` rendered recursively so components
+can nest.
+
+<ParametersTable {...renderGenerativeUI} />
 {/* api-reference:end */}

package/.docs/raw/docs/(reference)/api-reference/generative-ui/slack.mdx

@@ -0,0 +1,81 @@
+---
+title: Slack Block Kit
+description: "Convert generative UI trees to Slack Block Kit payloads and decode block_actions interactions back into $action payloads."
+---
+
+import { FromSlackBlocksResult, SlackBlocksResult, SlackConversionWarning, ToSlackBlocksOptions, decodeBlockAction, fromSlackBlocks, toSlackBlocks } from "@/generated/typeDocs";
+
+{/* AUTO-GENERATED PAGE by scripts/generate-api-reference.mts */}
+{/* Do not edit manually. */}
+
+{/* api-reference:start */}
+{/* AUTO-GENERATED by scripts/generate-api-reference.mts */}
+{/* Do not edit this block manually. */}
+
+## API Reference
+
+### decodeBlockAction
+
+Decodes one structural entry from a Slack `block_actions` payload.
+`$input` is reserved for the runtime selection: a `$input` key inside the
+button's JSON `value` payload is dropped rather than spread into the result.
+
+<ParametersTable {...decodeBlockAction} />
+
+### fromSlackBlocks
+
+Converts Slack Block Kit JSON back into a generative-ui IR tree, inverting
+[toSlackBlocks](/docs/api-reference/generative-ui/slack#toslackblocks). Accepts a blocks array or a `{ blocks }` wrapper;
+malformed input resolves to an empty node list plus a warning, and an
+unrecognized block or action element is skipped with a "dropped" warning.
+Every array read along the way (blocks, fields, options, elements, cards,
+rows, cells) is bounded to its site's cap before it is mapped over, so a
+hostile array (sparse or proxied with a fabricated `length`) is clamped
+with a "clamped" warning instead of stalling the event loop. Never throws.
+
+The Slack shape is lossier than the IR, so some information cannot be
+recovered: a context block's elements always decode as `Caption` (the
+original `Badge` vs `Caption` distinction does not survive the round trip),
+a button's `buttonStyle` is only recovered for the `primary`/`danger` Slack
+styles, a native alert block's `title` and `description` merge into a
+single `description` string, and a card's layout collapses to its `title`,
+a flat `children` list (image, then text, then caption, in that order),
+and `confirm`/`cancel` footer buttons. A section field's label and value
+are split on the first `*`+newline delimiter, so a label or value that
+itself contains that exact delimiter cannot be split back unambiguously.
+A data-table cell that Slack carries as `raw_text` always decodes as a
+string, even when its text is the stringified form of a boolean, since the
+Slack shape does not distinguish a boolean from ordinary text.
+
+<ParametersTable {...fromSlackBlocks} />
+
+### FromSlackBlocksResult
+
+The IR nodes and non-fatal warnings produced by converting Slack Block Kit JSON back into generative UI.
+
+<ParametersTable {...FromSlackBlocksResult} />
+
+### SlackBlocksResult
+
+The blocks and non-fatal warnings produced by Slack conversion.
+
+<ParametersTable {...SlackBlocksResult} />
+
+### SlackConversionWarning
+
+A non-fatal downgrade reported during Slack conversion.
+
+<ParametersTable {...SlackConversionWarning} />
+
+### toSlackBlocks
+
+Converts a generative-UI tree into Slack Block Kit JSON and downgrade warnings.
+
+<ParametersTable {...toSlackBlocks} />
+
+### ToSlackBlocksOptions
+
+Options that select the target Slack surface.
+
+<ParametersTable {...ToSlackBlocksOptions} />
+{/* api-reference:end */}

package/.docs/raw/docs/(reference)/api-reference/generative-ui/teams.mdx

@@ -0,0 +1,86 @@
+---
+title: Microsoft Teams
+description: "Convert generative UI trees to Teams Adaptive Cards and decode Action.Submit payloads back into $action payloads."
+---
+
+import { AdaptiveCardResult, TeamsAttachmentsResult, TeamsConversionWarning, decodeSubmitData, toAdaptiveCard, toTeamsAttachments } from "@/generated/typeDocs";
+
+{/* AUTO-GENERATED PAGE by scripts/generate-api-reference.mts */}
+{/* Do not edit manually. */}
+
+{/* api-reference:start */}
+{/* AUTO-GENERATED by scripts/generate-api-reference.mts */}
+{/* Do not edit this block manually. */}
+
+## API Reference
+
+### AdaptiveCardResult
+
+The card and non-fatal warnings produced by [toAdaptiveCard](/docs/api-reference/generative-ui/teams#toadaptivecard).
+
+<ParametersTable {...AdaptiveCardResult} />
+
+### decodeSubmitData
+
+Decodes the merged `activity.value` object a Teams bot receives on
+Action.Submit, inverting the `aui` envelope buildSubmitAction nests
+the resume action under. Adaptive Cards fold every other same-card input's
+value into the same submit object keyed by its `id`, so every top-level key
+besides `aui` is collected into `$input` (omitted when there are none).
+`aui` is reserved for the envelope: `toAdaptiveCard` renames any input
+whose id would collide to an unused id derived from it before encoding, so
+a same-card input value can never land on this key. `$input` and `type`
+are reserved on the way out: a `$input` key inside the envelope payload is
+dropped so the slot only ever reflects same-card input values, and the
+envelope's own `type` wins over a payload key of the same name. Every
+collected key (in `payload` or `$input`) is kept as an own data property of
+the returned object, even a `__proto__` or `constructor` key, since the
+object is always built by spreading and `Object.fromEntries` rather than by
+keyed assignment. Envelope keys are read as own properties only, so
+prototype-inherited `aui`, `type`, or `payload` values never dispatch.
+Returns `undefined` for a missing or malformed `aui` envelope; never throws.
+
+<ParametersTable {...decodeSubmitData} />
+
+### TeamsAttachmentsResult
+
+The attachments and non-fatal warnings produced by [toTeamsAttachments](/docs/api-reference/generative-ui/teams#toteamsattachments).
+
+<ParametersTable {...TeamsAttachmentsResult} />
+
+### TeamsConversionWarning
+
+A non-fatal downgrade reported during Teams conversion.
+
+<ParametersTable {...TeamsConversionWarning} />
+
+### toAdaptiveCard
+
+Converts a generative-ui tree into a Microsoft Teams Adaptive Card and
+non-fatal downgrade warnings. Sizes, weights, and colors map to Adaptive
+Card's semantic enums rather than raw values. An Input/Select/RadioGroup/
+Checkbox/DatePicker whose id would be the reserved RESERVED_INPUT_ID
+is renamed with a warning (see `decodeSubmitData`). Never throws: an
+unknown `$type` is skipped with a "dropped" warning, and a malformed input
+resolves to an empty card plus a "dropped" warning instead of throwing.
+
+<ParametersTable {...toAdaptiveCard} />
+
+### ToAdaptiveCardOptions
+
+Options accepted by [toAdaptiveCard](/docs/api-reference/generative-ui/teams#toadaptivecard) and [toTeamsAttachments](/docs/api-reference/generative-ui/teams#toteamsattachments). Reserved for future extension; no options are currently defined.
+
+```ts
+export interface ToAdaptiveCardOptions {}
+```
+
+### toTeamsAttachments
+
+Converts a generative-ui tree into Teams bot-framework message attachments.
+A root-level `Carousel` becomes one attachment per `Card` child (clamped to
+CAROUSEL_ATTACHMENT_CAP) with `attachmentLayout: "carousel"`;
+anything else converts through [toAdaptiveCard](/docs/api-reference/generative-ui/teams#toadaptivecard)'s engine into a
+single attachment. Never throws.
+
+<ParametersTable {...toTeamsAttachments} />
+{/* api-reference:end */}

package/.docs/raw/docs/(reference)/api-reference/generative-ui/tokens.mdx

@@ -0,0 +1,62 @@
+---
+title: Generative UI Tokens
+description: Shared token arrays used by the default generative UI vocabulary for sizing, color, alignment, and component variants.
+---
+
+{/* AUTO-GENERATED PAGE by scripts/generate-api-reference.mts */}
+{/* Do not edit manually. */}
+
+{/* api-reference:start */}
+{/* AUTO-GENERATED by scripts/generate-api-reference.mts */}
+{/* Do not edit this block manually. */}
+
+## API Reference
+
+### ALERT_TONES
+
+```ts
+const ALERT_TONES: readonly ["info", "success", "warning", "danger"];
+```
+
+### ALIGNS
+
+```ts
+const ALIGNS: readonly ["start", "center", "end"];
+```
+
+### BUTTON_STYLES
+
+```ts
+const BUTTON_STYLES: readonly ["primary", "secondary", "outline", "ghost", "danger"];
+```
+
+### COLORS
+
+```ts
+const COLORS: readonly ["emphasis", "secondary", "alpha-70", "white", "white-70", "white-50"];
+```
+
+### IMAGE_SIZE_TOKENS
+
+```ts
+const IMAGE_SIZE_TOKENS: readonly ["sm", "md", "lg"];
+```
+
+### JUSTIFIES
+
+```ts
+const JUSTIFIES: readonly ["start", "center", "end", "between"];
+```
+
+### TEXT_SIZES
+
+```ts
+const TEXT_SIZES: readonly ["sm", "md", "lg", "xl", "2xl", "3xl"];
+```
+
+### WEIGHTS
+
+```ts
+const WEIGHTS: readonly ["normal", "medium", "semibold", "bold"];
+```
+{/* api-reference:end */}

package/.docs/raw/docs/(reference)/api-reference/integrations/index.mdx

@@ -7,7 +7,7 @@ description: Package-level APIs for connecting assistant-ui React to the Vercel
 {/* The page list is generated from exported APIs; edit only the manual prose slot. */}
 
 {/* api-manual:start */}
-Integration packages connect assistant-ui to adjacent React and AI ecosystems. Use this section when you need the exact hooks, options, and helper exports for a package such as `@assistant-ui/react-ai-sdk`, `@assistant-ui/cloud-ai-sdk`, or `@assistant-ui/eve`.
+Integration packages connect assistant-ui to adjacent React and AI ecosystems. Use this section when you need the exact hooks, options, and helper exports for a package such as `@assistant-ui/react-ai-sdk`, `@assistant-ui/react-data-stream`, `@assistant-ui/cloud-ai-sdk`, or `@assistant-ui/eve`.
 {/* api-manual:end */}
 
 ## Pages
@@ -16,6 +16,9 @@ Integration packages connect assistant-ui to adjacent React and AI ecosystems. U
   <Card title={"@assistant-ui/react-ai-sdk"} href={"/docs/api-reference/integrations/react-ai-sdk"}>
     {"Vercel AI SDK runtime hooks, chat transports, and message conversion utilities for assistant-ui React applications."}
   </Card>
+  <Card title={"@assistant-ui/react-data-stream"} href={"/docs/api-reference/integrations/react-data-stream"}>
+    {"Data stream runtime hook and message conversion utilities for custom assistant-ui streaming backends."}
+  </Card>
   <Card title={"@assistant-ui/cloud-ai-sdk"} href={"/docs/api-reference/integrations/cloud-ai-sdk"}>
     {"Assistant Cloud AI SDK hooks for connecting cloud-backed threads, persistence, and chat state to assistant-ui React runtimes."}
   </Card>

package/.docs/raw/docs/(reference)/api-reference/integrations/react-ai-sdk.mdx

@@ -24,14 +24,14 @@ import { reactAiSdk_AISDKToolkit, reactAiSdk_AssistantChatTransport, reactAiSdk_
 
 ### createResumableSessionStorage
 
-`sessionStorage`-backed storage for the pending resumable stream id.
+`sessionStorage`-backed storage for the pending resumable stream id. See the [Resumable Streams](/docs/guides/resumable-streams) guide for end-to-end wiring.
 
 <ParametersTable {...reactAiSdk_createResumableSessionStorage} />
 
 ### frontendTools
 
 ```ts
-const frontendTools: (tools: Record<string, ToolJSONSchema>) => ToolSet;
+const frontendTools: (tools: FrontendTools) => ToolSet;
 ```
 
 ### getThreadMessageTokenUsage
@@ -63,6 +63,8 @@ export async function POST(req: Request) {
 
 ### RESUMABLE_STREAM_ID_HEADER
 
+Response header used by the [Resumable Streams](/docs/guides/resumable-streams) server and client wiring.
+
 ```ts
 const RESUMABLE_STREAM_ID_HEADER: "x-resumable-stream-id";
 ```

package/.docs/raw/docs/(reference)/api-reference/integrations/react-data-stream.mdx

@@ -0,0 +1,37 @@
+---
+title: "@assistant-ui/react-data-stream"
+description: Data stream runtime hook and message conversion utilities for custom assistant-ui streaming backends.
+---
+
+import { reactDataStream_toLanguageModelMessages, reactDataStream_useCloudRuntime, reactDataStream_useDataStreamRuntime } from "@/generated/integrationTypeDocs";
+
+{/* AUTO-GENERATED PAGE by scripts/generate-api-reference.mts */}
+{/* Do not edit manually. */}
+
+{/* api-reference:start */}
+{/* AUTO-GENERATED by scripts/generate-api-reference.mts */}
+{/* Do not edit this block manually. */}
+
+## API Reference
+
+### useDataStreamRuntime
+
+<ParametersTable {...reactDataStream_useDataStreamRuntime} />
+
+### toLanguageModelMessages
+
+<Callout type="warn">
+<strong>Deprecated.</strong> Use `toGenericMessages` from `assistant-stream` for framework-agnostic conversion.
+This function is kept for AI SDK compatibility.
+</Callout>
+
+<ParametersTable {...reactDataStream_toLanguageModelMessages} />
+
+### useCloudRuntime
+
+<Callout type="warn">
+<strong>Deprecated.</strong> This is under active development and not yet ready for prod use.
+</Callout>
+
+<ParametersTable {...reactDataStream_useCloudRuntime} />
+{/* api-reference:end */}

package/.docs/raw/docs/(reference)/api-reference/overview.mdx

@@ -3,6 +3,7 @@ title: API Reference
 description: Complete assistant-ui React API reference for building AI chat UIs with primitives, hooks, runtimes, adapters, tools, transport, voice, and integrations.
 ---
 
+{/* api-reference:skip-auto-generation */}
 
 import { Component, ContextLevel } from "./context";