Switch from OpenRouter without rewriting the client.
For supported chat requests, keep the OpenAI-compatible request shape and change three configuration values. Test one representative workload before moving more traffic.
The three-field migration
Keep the old configuration available until the new route passes your acceptance check.
| Field | OpenRouter | AIWave |
|---|---|---|
base_url | Your current OpenRouter endpoint | https://aiwave.live/v1 |
api_key | Your OpenRouter key | Your AIWave key from Console, stored server-side |
model | Your tested model ID | An exact current ID from Models |
Before you move traffic
Do not assume provider-specific fields, tool behavior, context limits, or rate semantics are identical. Send a redacted representative request, compare the response and request record, then keep bounded timeout, retry, and fallback rules in your application.
Verify the dated rate at /pricing or /api/v1/pricing. If the model ID is retired, copy a current ID instead of inventing an alias.