Ship one TypeScript integration for multiple AI providers and keep your routing policy outside the app code that talks to them.
Free preview, Starter for the Auto lane, Teams for manual GPT, Claude, and Gemini Pro access. Add-on credits kick in after included plan tokens are used.
Start on cheap auto-routed models first, then move up only when your workload truly needs premium manual control.
npm install llmwise
import { LLMWise } from "llmwise";
const client = new LLMWise("mm_sk_...");
const response = await client.chat({
model: "auto",
messages: [
{ role: "system", content: "Be concise." },
{ role: "user", content: "Explain eventual consistency in two sentences." },
],
});
console.log(response.model);
console.log(response.content);
console.log(response.cost_usd);Everything you need to integrate LLMWise's multi-model API into your TypeScript project.
Use the TypeScript client when you want a minimal wrapper around the same API your product uses in production. It keeps your app code focused on workflow logic instead of provider-specific plumbing.
npm install llmwise
Initialize the client with your `mm_sk_...` key and reuse it anywhere you need chat, compare, or routed requests. One key gives you access to the full multi-model surface.
import { LLMWise } from "llmwise";
const client = new LLMWise("mm_sk_...");Keep TypeScript integrations simple by defaulting to `model: "auto"`. You can still pin a specific model later, but Auto is the quickest way to get working behavior with sensible cost control.
const response = await client.chat({
model: "auto",
messages: [{ role: "user", content: "Classify this support ticket." }],
});When you are deciding between providers for a feature, compare mode helps you test model quality without switching SDKs or auth flows. This is especially useful in TypeScript products where experimentation speed matters.
const comparison = await client.compare({
model: "auto",
messages: [{ role: "user", content: "Write release notes for this patch." }],
});As your app grows, keep the same TypeScript client while changing routing and billing policy in LLMWise. That is the main advantage of a unified API layer: your application code stays stable while your infrastructure choices evolve.
Free preview, Starter for the Auto lane, Teams for manual GPT, Claude, and Gemini Pro access. Add-on credits kick in after included plan tokens are used.
Start on cheap auto-routed models first, then move up only when your workload truly needs premium manual control.
Pricing changes, new model launches, and optimization tips. No spam.