Migration from OpenRouter

Documentation Index

Fetch the complete documentation index at: https://docs.ai-stats.phaseo.app/llms.txt

Use this file to discover all available pages before exploring further.

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.
• AI_STATS_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." }],
});

​

3) Validate model IDs and remove OpenRouter-only behavior

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

• Keep Authorization: Bearer format unchanged.
• Remove legacy gateway-specific headers unless you still need them.
• 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.

​

4) OpenRouter parity checklist

• Base URL updated to https://api.phaseo.app/v1.
• OPENROUTER_API_KEY replaced with AI_STATS_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.

​

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 $AI_STATS_API_KEY"
curl -s "https://api.phaseo.app/v1/chat/completions" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer $AI_STATS_API_KEY" \
  -d '{"model":"openai/gpt-4.1-mini","messages":[{"role":"user","content":"Say hello"}]}'

• 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

• Quickstart
• API Reference: Models
• Examples
• Error Handling