This guide uses source checks from Sep 24, 2026. Provider and gateway prices can change; preserve the checked date with every forecast.
Why This Topic Matters Now
The Sep 23 report surfaced `responses api streaming` alongside `chat completion stream`. The migration question is broader than transport: a client may accept a familiar SDK call while changing input objects, output parsing, tool calls, usage accounting, and retry safety. Treat the Responses API as a contract to verify, not as a drop-in label.
This checklist is for Tier 1 and Tier 2 teams evaluating DeepSeek routes through an OpenAI-compatible gateway. It separates DeepSeek's provider documentation from AIWave's public route evidence, keeps Chat Completions and Responses API claims distinct, and turns a migration into a bounded canary with a reversible decision record. The result should explain both what worked and which capability remains unverified.
Source Facts Checked Today
AIWave /api/pricing was checked from production on Sep 24, 2026 and returned HTTP 200, success=true, 73 live route rows, pricing_version a42d372ccf0b5dd13ecf71203521f9d2, auto_groups=['default'], group_ratio default=1 and vip=0.9. The public /api/v1/pricing endpoint returned HTTP 200 with 56 dated USD rows, pricing_version 83f77abde81ee3a096a672ed959ccc096f5d37a45c177ae8e03229456b5415a5, checked=2026-09-10, and updated_at=2026-09-18. Use the live response for route availability and the dated JSON for a forecast; they are not one interchangeable rate table.
DeepSeek's Responses API guide checked on Sep 24, 2026 documents a Responses API path and request concepts. The article uses that page to define provider-side terminology; it does not infer that every provider feature is exposed by every AIWave endpoint.
DeepSeek's models and pricing page checked on Sep 24, 2026 lists separate model capabilities, context details, and token price columns. Its current page distinguishes OpenAI-format access from other interfaces, so preserve endpoint and model evidence together in a migration record.
The dated AIWave pricing JSON checked in this run lists deepseek-flash at $0.70 input, $0.0233 cache-hit input, and $2.10 output per 1M tokens, effective 2026-09-10. It lists deepseek-v4-pro at $1.914 input, $0.0637362 cache-hit input, and $5.742 output per 1M tokens, effective 2026-08-27. These are dated gateway base-rate rows, not a direct-provider invoice.
Planning Matrix
A source-dated planning matrix keeps the page useful for engineers and procurement reviewers. It turns a search query into an auditable route decision instead of a loose model preference.
| Migration surface | Failure mode | Acceptance evidence |
|---|---|---|
| Input shape | Messages and input items are silently mixed | Redacted fixture and parsed request |
| Output parsing | Text is present but typed output is lost | Parser result and schema check |
| Tools | A tool call is treated as final text | Tool fixture and state transition |
| Usage | Forecast misses cached or output tokens | Receipt fields and source date |
| Errors | Provider error becomes a generic retry | Status, code, request ID, stop reason |
| Fallback | A partial response is duplicated | Attempt ceiling and idempotency rule |
Implementation Pattern
The implementation pattern keeps credentials as placeholders, pins the AIWave base URL, records the model, and leaves room for route-specific controls. Production applications should move credentials into environment or secret storage.
from openai import OpenAI
client = OpenAI(
api_key="YOUR_API_KEY_HERE",
base_url="https://aiwave.live/v1",
)
policy = {
"model": "deepseek-v4-pro",
"interface": "chat-completions",
"max_tokens": 240,
"checked_at": "2026-09-24",
}
result = client.chat.completions.create(
model=policy["model"],
messages=[{"role": "user", "content": "Return one bounded migration check."}],
temperature=0.0,
max_tokens=policy["max_tokens"],
)
print({"interface": policy["interface"], "finish": result.choices[0].finish_reason,
"usage": result.usage, "request_id": getattr(result, "id", None)})
Turn the Query Into a Contract
For a DeepSeek Responses API migration, define the request shape, model ID, data class, output ceiling, timeout, retry ceiling, owner, and source date before the first trial. A short contract gives engineering, security, and finance the same object to review when a provider changes a route or billing field.
Separate Live Routes From Dated Rates
The live AIWave pricing response answers which route rows and endpoint types are available at check time. The public pricing JSON is a dated USD snapshot for forecasting. Store both URLs, versions, checked dates, model IDs, and account-group context instead of presenting a volatile source as a permanent quote.
Use a Small Acceptance Set
A useful canary covers a normal request, a malformed request, a repeated prefix, a long output, a disconnect, and a deliberate stop condition. Record request ID, model ID, status, token usage, finish reason, retry count, and reviewer outcome. This turns a search result into evidence that can survive a route update.
Keep Data and Credentials Bounded
OpenAI-compatible clients reduce integration work, but they do not choose the right data boundary. Keep the credential server-side, use a visible placeholder in examples, redact fixtures, and attach a data-class decision to every route policy. Do not let a feature flag or model alias silently widen what crosses the API.
Make Recovery Observable
Retry only failures that are safe to retry and cap every fallback. Preserve the original request ID, mark the stop reason, and distinguish provider errors from client validation, policy rejection, and budget stops. Silent loops hide both reliability failures and billing variance.
Use AIWave's Evidence Layer
Use the Chat Completions docs, Models docs, dated Pricing JSON, and Status. Recheck the live route table before rollout, the dated pricing JSON before a budget review, the status page before a launch window, and the trust page before procurement. Keep each checked date visible in the record.
Release Gate
Promotion is ready when the provider source is dated, the AIWave route is rechecked, the acceptance set passes, the billing fields are understood, and a named owner can stop or reverse the change. If a field is unknown, label the work as a trial rather than production.