This guide uses source checks from Sep 20, 2026. Provider and gateway prices can change; preserve the checked date with every forecast.
Why This Topic Matters Now
The market section of the Sep 19 report emphasized that Tier 1 buyers care about production cost volatility, route evidence, trust, and compliance rather than a static model list. For a SaaS release team, the practical artifact is a route change-control record that explains what changed, why it changed, what was tested, and how to return to the prior route.
A route can change even when the SDK does not. A new model ID, a different fallback, a changed cache field, a new key group, or a refreshed price snapshot can alter behavior and spend. Treat the live route endpoint and the dated public price JSON as separate inputs to the release gate, with the source dates visible to reviewers.
Source Facts Checked Today
AIWave /api/pricing was checked from production on Sep 20, 2026 and returned HTTP 200, success=true, 68 live route rows, pricing_version a42d372ccf0b5dd13ecf71203521f9d2, auto_groups=['default'], and group_ratio default=1 and vip=0.9. The public /api/v1/pricing endpoint also returned HTTP 200 with 56 dated USD rows, pricing_version 83f77abde81ee3a096a672ed959ccc096f5d37a45c177ae8e03229456b5415a5, updated_at=2026-09-18, and row checked dates of 2026-09-10. Use the live endpoint for route and group evidence, and the static endpoint for dated public USD rates.
The dated public JSON includes DeepSeek V4 Flash at $0.638 input, $0.0202884 cache-hit input, and $1.914 output; GLM 5.1 at $2.1, $0.680001, and about $6.6; and Kimi K3 at $4.5, $0.9, and $22.5 per 1M tokens. These figures are useful for change review only when their checked and effective dates remain attached.
The live route response exposes OpenAI-compatible endpoint types and current route-governance fields for the reviewed model IDs. Use it to verify that a manifest still points at an active route, but do not infer provider retention, regional processing, or SLA commitments from that row.
DeepSeek, QwenCloud, and Z.AI documentation describe provider-side pricing and capability concepts. A SaaS release record should retain the provider URL, AIWave URL, exact model ID, source date, test result, and rollback owner as separate fields.
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.
| Change field | Review question | Rollback trigger |
|---|---|---|
| Model ID | Is the exact ID active and approved? | catalog or route mismatch |
| Price source | Are checked and effective dates recorded? | stale or conflicting row |
| Prompt class | Does the data class fit the route policy? | privacy review failure |
| Canary | Did representative tests pass? | schema, quality, or error regression |
| Fallback | Is the alternate route bounded and tested? | loop or unsafe retry |
| Rollback | Who can stop and restore the prior manifest? | no named owner |
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 dataclasses import dataclass
from openai import OpenAI
client = OpenAI(api_key="YOUR_API_KEY_HERE", base_url="https://aiwave.live/v1")
@dataclass
class RouteChange:
old_model: str
new_model: str
source_checked: str
canary_passed: bool
rollback_owner: str
def canary(model: str, prompt: str) -> dict:
response = client.chat.completions.create(
model=model, messages=[{"role": "user", "content": prompt}],
temperature=0.0, max_tokens=160,
)
return {"model": model, "finish": response.choices[0].finish_reason,
"tokens": response.usage.total_tokens}
Write the Decision Record First
For Chinese AI API route change control, record the workload, approved model IDs, endpoint, source date, output cap, retry ceiling, data class, budget owner, and fallback before traffic moves. A short decision record makes a later model or price change reviewable instead of surprising.
Keep Provider and Gateway Evidence Separate
Provider documentation describes direct-platform capabilities and billing concepts. AIWave endpoints describe the gateway's current route rows, public USD snapshot, supported endpoint type, and key-group context. A route row is not a promise that every provider feature is exposed or that a provider policy transfers automatically to the gateway.
Use a Representative Acceptance Set
Test one ordinary request, one long-context request, one malformed request, and one stop-condition request. Store model, finish reason, token usage, retry count, request identifier, checked source date, and reviewer decision. Do not promote a route because a single demo looked good.
Budget Input, Cache, and Output Independently
A single token total hides the cause of a bill. Store input tokens, cached input when exposed, output tokens, tool calls, and retries in separate fields. A route's output cap should follow the task class rather than a global default inherited by every feature.
Bound Retries and Fallbacks
Retry only errors that are safe to retry, use an attempt ceiling, and preserve the request ID. A fallback must be selected by policy, not by an unbounded loop. The receipt should show the original route, fallback route, stop reason, and whether the output was accepted or revised.
Use AIWave's Evidence Layer
Use the live route pricing, dated Pricing JSON, Status, Trust, and Models docs. Read the live route table before a rollout, the dated pricing JSON before a budget review, the status page before a launch window, and the trust page before procurement review. Keep the checked dates in the internal decision record.
Final Promotion Checklist
Promotion is ready when provider sources are dated, AIWave routes are rechecked, public USD rows carry their own checked dates, canaries pass, output and retry limits exist, privacy handling is documented, and a reviewer can reconcile the receipt without seeing a prompt or reusable key.