Quickstart

Create an account, add an agent, and publish it. Publishing is what gives the agent a model, a system prompt, a theme, and its enabled features.

Copy the agent’s server key. It looks like mck_live_… and is read only on your server — never ship it to the browser.

MORDN_CHAT_KEY="mck_live_..."
# Local development or deployments without managed AI Gateway credentials:
AI_GATEWAY_API_KEY="your_ai_gateway_key"

Set the required secrets in your deployment environment too. Neither key belongs in a NEXT_PUBLIC_ variable or client component.

npm install @mordn/chat-widget ai @ai-sdk/react

These are the chat dependencies to add to your existing authenticated app. This path needs no database driver, storage SDK, or model-provider package. The published agent config supplies a model identifier, not model credentials.

import { createMordnHandler } from '@mordn/chat-widget/server';
import { auth } from '@clerk/nextjs/server';

export const { GET, POST, DELETE, OPTIONS } = createMordnHandler({
  apiKey: process.env.MORDN_CHAT_KEY!,
  getUserId: async () => (await auth()).userId,
});

apiKey and getUserId are the only required options. That one key wires persistence, private attachments, published configuration, knowledge retrieval, memory, hosted MCP tools, and feedback. Feature behavior depends on your published configuration; the key does not replace your model credentials.

Swap the Clerk import for whatever you already use. The contract is the same: return a stable user id from a verified server session, or null.

import { auth } from '@/auth';

getUserId: async () => (await auth())?.user?.id ?? null,

'use client';

import { ChatWidget } from '@mordn/chat-widget';
import '@mordn/chat-widget/styles.css';

export function Assistant() {
  return <ChatWidget />;
}

That is the whole component. apiBase defaults to /api/chat; pass it explicitly if you mounted the route somewhere else.

On mount the widget calls GET ${apiBase}/bootstrap and the server returns only what the browser is allowed to see — greeting, theme, layout, features, starter prompts. The widget never sends a userId, so it cannot assert who it is or whose history it may read.

Render <Assistant /> inside a signed-in page or layout, sign in, and type. The first message creates the conversation; reload the page and it is still there.