alibaba
Package
Section titled “Package”@ai-sdk/alibaba
Factories
Section titled “Factories”AIProviders.alibaba
Capabilities
Section titled “Capabilities”- Language
- Embedding
- Video
Forward-compatible Wan video routing
Section titled “Forward-compatible Wan video routing”Wan video requests choose their protocol from the numeric model version. Known wan2.6 and earlier IDs, including the older wanx2.1 prefix, retain legacy size fields. Wan 2.7 and later 2.x models use the tiered reference protocol. Wan 3+, and unrecognized future IDs, inherit the latest all-in-one media protocol with media inputs, tiered resolution and ratio handling.
Alibaba mirrors upstream 2.0.76: ALIBABA_API_KEY, versioned user-agent suffix, chat/language callable aliases, DashScope chat completions with thinking/reasoning mapping, generated fallback IDs for missing tool-call IDs, cache-aware usage with nonnegative reasoning-adjusted output text tokens, historical assistant reasoning omission including removal of reasoning-only turns, DashScope embedding endpoint with dense and sparse option mapping, video submit/poll flow, wan2.6 legacy video protocol, wan2.7 media/ratio video protocol, WAN 3 all-in-one media/resolution/aspect-ratio/audio mapping and usage metadata, provider option validation, warnings, provider metadata, and unsupported image families. ProviderV4 type names, ESM-only packaging, Node 22 engines, and workflow serialization helpers are JS-only upstream concerns. The 2026-09-20 pass adds typed preserveThinking, model-aware defaults, and assistant reasoning-history replay. The 2026-09-27 pass adds model-aware Qwen 3.7/3.8 JSON Schema routing and preserves unsupported-structured-output warnings for other model families. The 2026-10-11 pass: Common max reasoning uses a 95 percent token budget; embedding dimensions default from the shared request and provider dimension overrides it. The 2026-10-18 pass: Wan video routing parses numeric versions: pre-2.7 IDs retain legacy requests, later 2.x IDs use the Wan 2.7 tiered protocol, and 3+ or unknown future IDs use the current all-in-one media protocol. The 2026-10-23 pass: Polling and status resource IDs are encoded as one path segment, including reserved characters and standalone dots.
Factory argument requirements are defined by the public Swift factory signatures. Use Public symbols when you need the exact initializer or factory declaration.
Return to the provider matrix.