IntegrationTypeScript

LLM API for TypeScript

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.

Why teams start here first
Free preview
5 messages to try it
No card required to see how Auto routing feels before you commit.
Starter
Auto lane only
Curated cheap model pool with no manual premium-model selection.
Teams
Premium when you need it
Manual GPT, Claude, and Gemini Pro access starts here.
Billing
Plan tokens first
Add-on credits only extend usage after included plan tokens are exhausted.
Quick start
npm install llmwise

Full example

TypeScript
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);
Evidence snapshot

TypeScript integration overview

Everything you need to integrate LLMWise's multi-model API into your TypeScript project.

Setup steps
5
to first API call
Features
6
capabilities included
Models available
9
via single endpoint
Free preview
Available
see pricing for current included usage

What you get

+Single TypeScript client for multiple model providers
+Auto routing for cheap-by-default production behavior
+Compare mode for evaluation workflows and model selection
+OpenAI-style request shapes that fit existing chat apps
+BYOK support for direct provider billing where needed
+Model, latency, and cost metadata returned with each request

Step-by-step integration

1Install the package

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
2Create the client once

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_...");
3Call chat with Auto routing

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." }],
});
4Use compare mode while you tune workflows

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." }],
});
5Scale up with BYOK and failover policy

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.

Common questions

Why use a unified LLM API from TypeScript?
Because it keeps provider choice out of your application code. You can swap routing policy, billing mode, and even default models without rewriting your TypeScript integration every time product requirements change.
Is the TypeScript API OpenAI-style?
The request shape is designed to feel familiar if you already use role/content chat messages, which makes migration much easier for existing AI apps.
Can I compare models from one TypeScript call?
Yes. Compare mode is built into the same integration surface, so you can test multiple model outputs without wiring extra SDKs or service wrappers.
Can I mix BYOK and pooled billing from TypeScript?
Yes. The TypeScript client stays the same while LLMWise decides whether a request should use your own provider key or pooled platform access.

Start on Auto, move up only when you need it

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.

Starter Auto laneTeams premium manual accessPlan tokens + add-ons
Get LLM insights in your inbox

Pricing changes, new model launches, and optimization tips. No spam.