Home/Migrate/From OpenRouter
Migration guide · 5 minutes

OpenRouter → QuickSilver Pro

Two lines of code. ~20% cheaper on DeepSeek V4 Flash + Pro, V3, R1, Qwen 3.7 Max + 3.6 Plus + 3.6 + 3.5, and Kimi K2.6. For the comparative analysis, see /vs/openrouter.

The 5 steps

  1. 1

    Get a QuickSilver Pro API key

    Sign up at quicksilverpro.io/dashboard. Launch bonus: top up between $5 and $50 and we match it 100% — pay $5, get $10; pay $50, get $100.

  2. 2

    Change the base URL

    In your OpenAI SDK init, swap the base_url.

    - base_url="https://openrouter.ai/api/v1"
    + base_url="https://api.quicksilverpro.io/v1"
  3. 3

    Swap the API key

    Replace OPENROUTER_KEY with your QSP key.

    - api_key=os.environ["OPENROUTER_KEY"],
    + api_key=os.environ["QSP_KEY"],
  4. 4

    Rename model IDs

    Drop the provider/ prefix. The Qwen models also drop the trailing -a3b MoE-config suffix.

    OpenRouterQuickSilver Pro
    deepseek/deepseek-v4-flashdeepseek-v4-flash
    deepseek/deepseek-v4-prodeepseek-v4-pro
    deepseek/deepseek-chatdeepseek-v3
    deepseek/deepseek-r1deepseek-r1
    qwen/qwen3.7-maxqwen3.7-max
    qwen/qwen3.7-plusqwen3.7-plus
    qwen/qwen3.6-plusqwen3.6-plus
    qwen/qwen3.6-35b-a3bqwen3.6-35b
    qwen/qwen3.5-35b-a3bqwen3.5-35b
    moonshotai/kimi-k2.6kimi-k2.6
    moonshotai/kimi-k2.7-codekimi-k2.7-code
    z-ai/glm-5.2glm-5.2
  5. 5

    Test your core flows end-to-end

    Run one representative request for each feature — chat, tool_calls, json_schema strict mode, streaming. Any behavioral diff is a bug — report it.

Full before/after

Before · OpenRouter
from openai import OpenAI

client = OpenAI(
    base_url="https://openrouter.ai/api/v1",
    api_key=os.environ["OPENROUTER_KEY"],
)

r = client.chat.completions.create(
    model="deepseek/deepseek-chat",
    messages=[{"role": "user", "content": "Hi"}],
)
After · QuickSilver Pro
from openai import OpenAI

client = OpenAI(
    base_url="https://api.quicksilverpro.io/v1",
    api_key=os.environ["QSP_KEY"],
)

r = client.chat.completions.create(
    model="deepseek-v3",
    messages=[{"role": "user", "content": "Hi"}],
)

Common migration pitfalls

Cache-hit ratio drops temporarily
OpenRouter's cache lives across upstream providers; when you switch to QSP your cache starts cold. For the first day or two, observed cost may be a few % higher than list-price math suggests. Cache fills within 24-48h of your normal traffic pattern.
Model version drift
OpenRouter's deepseek/deepseek-chat occasionally points to different DeepSeek V3 revisions. QSP routes deepseek-v3 to a specific revision. If your evals were tuned to a particular output style, re-run them after switching.
Don't migrate models you don't use on QSP
QSP's catalog is 9 open-source LLMs (DeepSeek V4 Flash + Pro, V3, R1, Qwen 3.7 Max, 3.6 Plus, 3.6 + 3.5 35B-A3B, Kimi K2.6) plus Gemini. If your OpenRouter setup also uses GPT-4, Claude, Llama, or Mistral — keep calling OpenRouter for those. Many teams run both SDKs side-by-side.
Rate limits work differently
OpenRouter silently smooths across upstreams. QSP enforces per-key throughput caps (default 600 req/min, 1M tok/min, 8 parallel). For bursty workloads, enable retry-on-429 in your client and ask for a higher limit if needed.

Other migration guides

Need help?

Email hello@quicksilverpro.io — a human replies usually within 4 hours. For the broader analysis, see QuickSilver Pro vs OpenRouter.

Start saving in 5 minutes

Launch bonus: first deposit matched 100%, up to $50 free. Keep your OpenAI SDK unchanged — only the URL and key change.

Get API Key