Installation

@deuz-sdk/core is a single package with zero runtime dependencies. Install it, and the chat core, the agentic tool loop, streaming, and the canonical UI wire are all available out of the box. Heavier or stateful capabilities (schema-typed objects, MCP, document parsing) pull in optional peers only when you actually use them.

Install

npm install @deuz-sdk/core

pnpm add @deuz-sdk/core

yarn add @deuz-sdk/core

bun add @deuz-sdk/core

Requirements

The core is pure and web-first: it touches only Web APIs (fetch, Web Streams, TextDecoder, WebCrypto, atob/btoa). Anything stateful or non-deterministic — HTTP, clock, logging, metering, circuit-breaker, API keys, id generation — is injected through a single Dependencies seam, with no-op/in-memory defaults applied for you. As a result the same build runs unchanged on any runtime that has fetch plus Web Streams.

Node-only capabilities (filesystem skill sources, document parsers, the markdown memory vault, MCP stdio transport) live behind dedicated …/node subpaths and never leak node:* imports into the edge-safe core.

Zero runtime dependencies

The package ships nothing in dependencies. The chat core, resilience, metering, the four provider wires, the agentic loop, and the UI wire all run on Web APIs alone. The only things you may need to add are optional peers, and only for the specific features that use them.

Optional peer dependencies

Install a peer only when you reach for the feature in its row. Each is declared optional in peerDependenciesMeta, so package managers will not nag you for the ones you skip.

npm install zod @standard-community/standard-json

npm install @modelcontextprotocol/sdk

npm install unpdf mammoth xlsx

The rag/node parsers are independent — install only the formats you need. The RAG core (MIME sniffing, chunkers, retrieve/rerank, BM25, RRF) is edge-safe and needs no peers; only the Node document parsers do.

Subpath exports

The root export carries the free functions, the client, errors, and all canonical types. Everything else is a focused subpath so bundlers tree-shake what you don't import.

Verify it works

API keys are read from the environment at your app layer and passed into the provider factory — the SDK core never reads process.env itself.

import { streamChat } from '@deuz-sdk/core';
import { createAnthropic } from '@deuz-sdk/core/anthropic';

const anthropic = createAnthropic({ apiKey: process.env.ANTHROPIC_API_KEY! });

// streamChat returns synchronously; the request starts lazily on first access.
const res = streamChat({
  model: anthropic('claude-opus-4-8'),
  messages: [{ role: 'user', content: 'Say hello in one word.' }],
});

for await (const chunk of res.textStream) process.stdout.write(chunk);

const usage = await res.usage; // resolves when the stream finishes
console.log(`\n${usage.inputTokens} in / ${usage.outputTokens} out`);

res.textStream is an AsyncIterable<string> and res.usage is a Promise<Usage> — both are explained in streamChat.

Edge-safe subset

When you target Cloudflare Workers or Vercel Edge and want a build that is provably free of any Node API, import from the /edge entry. It re-exports the same streamChat / generateText / generateObject, the client, the base errors, and all types.

import { streamChat } from '@deuz-sdk/core/edge';
import { createAnthropic } from '@deuz-sdk/core/anthropic';
import { toDeuzStreamResponse } from '@deuz-sdk/core/ui';

export const runtime = 'edge';

const anthropic = createAnthropic({ apiKey: process.env.ANTHROPIC_API_KEY! });

export async function POST(req: Request) {
  const { messages } = await req.json();
  const res = streamChat({ model: anthropic('claude-opus-4-8'), messages });
  return toDeuzStreamResponse(res); // versioned Deuz UI wire
}

ESM and CJS

Every subpath ships both an ESM (import) and a CommonJS (require) build with matching .d.ts / .d.cts declarations, so the package resolves correctly under "moduleResolution": "Bundler", "Node16", or "NodeNext". It is authored against TypeScript strict mode (including noUncheckedIndexedAccess), so the public types are strict-ready in your project with no extra configuration.

import { generateText } from '@deuz-sdk/core';

const { generateText } = require('@deuz-sdk/core');

Next steps

• streamChat — the synchronous, never-throws streaming entry point.
• generateText — buffered text plus the agentic tool loop.
• generateObject — schema-typed structured output.
• Providers — Anthropic, OpenAI, xAI, Gemini, Vertex, Yunwu, Voyage.