Migrate from OpenRouter to Phaseo

​

What changes

1. Keep payload shape unchanged.
2. Swap base URL and API key source.
3. Verify model IDs and any OpenRouter-only headers.
4. Roll traffic gradually while comparing latency, output, and cost behavior.

​

Before you start

• Access to the current OpenRouter integration code and deployment config.
• PHASEO_API_KEY available in dev, staging, and production.
• A short list of production model IDs and representative prompts.

​

1) Inventory current OpenRouter usage

• Find openrouter.ai endpoint references.
• Find OPENROUTER_API_KEY usage in code, CI, and hosting env vars.
• Find OpenRouter-only headers such as HTTP-Referer and X-Title.
• Document active model IDs and any fallback-chain logic.
• Document any reusable prompt, provider, or parameter defaults that should move into Gateway presets instead of staying duplicated in application code.

​

2) Swap base URL and credentials

// Before
import OpenAI from "openai";

const before = new OpenAI({
  apiKey: process.env.OPENROUTER_API_KEY,
  baseURL: "https://openrouter.ai/api/v1",
});

const response = await before.chat.completions.create({
  model: "openai/gpt-4.1-mini",
  messages: [{ role: "user", content: "Summarize our migration plan." }],
});

// After
import OpenAI from "openai";

const after = new OpenAI({
  apiKey: process.env.PHASEO_API_KEY,
  baseURL: "https://api.phaseo.app/v1",
});

const response = await after.chat.completions.create({
  model: "openai/gpt-4.1-mini",
  messages: [{ role: "user", content: "Summarize our migration plan." }],
});

# Before
curl -s "https://openrouter.ai/api/v1/chat/completions" \
  -H "Authorization: Bearer $OPENROUTER_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "openai/gpt-4.1-mini",
    "messages": [{"role":"user","content":"Say hello"}]
  }'

# After
curl -s "https://api.phaseo.app/v1/chat/completions" \
  -H "Authorization: Bearer $PHASEO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "openai/gpt-4.1-mini",
    "messages": [{"role":"user","content":"Say hello"}]
  }'

​

3) Validate model IDs and map OpenRouter-only behavior

curl -s "https://api.phaseo.app/v1/models" \
  -H "Authorization: Bearer $PHASEO_API_KEY" | jq '.data[0:10] | map(.id)'

• Keep Authorization: Bearer format unchanged.
• Keep HTTP-Referer and X-Title when they identify the calling application. Phaseo accepts the lowercase equivalents http-referer and x-title.
• If callers depend on OpenRouter-only response fields, adapt them in one compatibility layer instead of changing every caller.
• If your OpenRouter setup relies on provider allow/deny lists or routing defaults, map those into Presets and Routing and Fallbacks instead of scattering them across callers.

​

Map provider controls

​

4) OpenRouter parity checklist

• Base URL updated to https://api.phaseo.app/v1.
• OPENROUTER_API_KEY replaced with PHASEO_API_KEY in all environments.
• All production model IDs verified against /v1/models.
• One non-streaming request validated through /v1/chat/completions or /v1/responses.
• One streaming request validated through the same app-level integration path used in production.
• Generation lookups rechecked through GET /v1/generations?id=<request_id> so failed requests can be replayed from the stored replay_request payload when replay_supported=true.
• Tool-calling and structured-output flows rechecked with real prompts.
• Invalid-key and invalid-model failures verified in staging.
• Any OpenRouter-only headers or response fields either removed or explicitly normalized.
• Shared prompt/routing defaults moved into presets where appropriate.

​

Agent migration checklist

1. Search runtime code and deployment config for openrouter.ai, OPENROUTER_API_KEY, sk-or-v1, HTTP-Referer, and X-Title.
2. Change the client boundary to https://api.phaseo.app/v1 and PHASEO_API_KEY without adding a secret value to source control.
3. Query GET /v1/models and record every old-to-new model mapping.
4. Adapt OpenRouter-only routing options or response fields in one compatibility module.
5. Run the health, models, non-streaming, streaming, and failure-path checks below.
6. Report changed files, secret-name changes, model mappings, test evidence, parity gaps, and the rollback switch.

​

5) Roll out safely

1. Start with internal traffic only.
2. Move to 5-10% production traffic and compare quality, latency, and cost metrics.
3. Promote to 100% only after parity is confirmed.
4. Keep rollback as a config-only endpoint/key switch until the cutover is stable.

​

Validation commands

curl -s "https://api.phaseo.app/v1/health"
curl -s "https://api.phaseo.app/v1/models" -H "Authorization: Bearer $PHASEO_API_KEY"
curl -s "https://api.phaseo.app/v1/chat/completions" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer $PHASEO_API_KEY" \
  -d '{"model":"openai/gpt-4.1-mini","messages":[{"role":"user","content":"Say hello"}]}'

curl -N "https://api.phaseo.app/v1/chat/completions" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer $PHASEO_API_KEY" \
  -d '{"model":"openai/gpt-4.1-mini","stream":true,"messages":[{"role":"user","content":"Reply with: stream works"}]}'

curl -s "https://api.phaseo.app/v1/chat/completions" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer $PHASEO_API_KEY" \
  -d '{"model":"invalid/migration-test","messages":[{"role":"user","content":"test"}]}'

• Run one streaming request through your app-level integration test.
• Run one negative test for invalid key or invalid model.
• Replay a small golden prompt set and compare outputs to baseline.

​

Next steps

• Get free help migrating your OpenRouter integration
• Open the interactive OpenRouter migration guide
• Compare Phaseo and OpenRouter
• Quickstart
• API Reference: Models
• Examples
• Error Handling