Migrate from OpenRouter

Swap one line — the baseURL — and your existing model slugs keep working.

Swap the baseURL

Migration is one line: swap the baseURL. Nothing else changes.

One-line diff

import OpenAI from "openai";

const client = new OpenAI({
-  baseURL: "https://openrouter.ai/api/v1",
+  baseURL: "https://router-api.intelli-verse-x.ai/v1",
  apiKey: process.env.INTELLIVERSE_API_KEY,
});

// Unchanged call sites keep working:
await client.chat.completions.create({
  model: "anthropic/claude-sonnet-4", // mapped into your tier's routing
  messages: [{ role: "user", content: "..." }],
});

Legacy model slugs

Your existing OpenRouter-style model slugs keep working — we never error on anthropic/*, openai/*, google/*, meta-llama/*, mistralai/*, deepseek/*, qwen/*, or openrouter/auto. Each slug is transparently mapped into your plan's tier routing (the request is classified and routed inside your tier's pool like any other; responses report your tier alias), so you can migrate without touching call sites and remove the slugs at your own pace.

Note

Once migrated, prefer the tier aliases (or omit model entirely) — see Models & tiers.

Audit your migration

Every mapped slug is recorded in your request logs from your first call, so you can audit exactly which legacy call sites are still sending slugs. A 7-day migration cost estimate (your traffic here vs. a conservative OpenRouter list-price blend) lives on Dashboard → Activity when you are signed in, and on /compare/openrouter with methodology — no fabricated numbers.