DOCS
Models
The catalog is on the runtime. The client may pass model or provider on a turn; failover is still the ordered list.
Builtin ids
Catalog lives on the runtime, not in the JS client. Default id
deepseek-v4-flash-responses.
Default failover list is
deepseek-v4-flash-anthropic.
Alias
deepseek-v4-flash
resolves to the Responses entry.
Product:
models.
deepseek-v4-flash-responses DeepSeek V4 Flash (Responses)
Default. Protocol Responses. API model deepseek-v4-flash. Alias deepseek-v4-flash.
deepseek-v4-flash-anthropic DeepSeek V4 Flash (Anthropic)
Default failover. Protocol Anthropic. API model deepseek-v4-flash.
deepseek-v4-pro DeepSeek V4 Pro
Protocol Responses. API model deepseek-v4-pro.
Protocols
Custom catalog entries set
protocol
to
responses
or
anthropic,
plus
url,
key, and
api_model.
The HTTP client posts to:
Responses POST {url}/responses
Anthropic POST {url}/messagesEnv
-
DEEPSEEK_API_KEY(orSVEDA_DEEPSEEK_API_KEY) fills the builtin DeepSeek keys. -
SVEDA_DEFAULT_MODELsetsdefault_id. -
SVEDA_FAILOVERis a comma-separated list of catalog ids, walked after the primary.
Failover is ordered: primary model first, then
failover_ids.
The client still calls
session.send
once. Stream event types do not change.
Model failover.
export DEEPSEEK_API_KEY=sk-...
export SVEDA_DEFAULT_MODEL=deepseek-v4-flash-responses
export SVEDA_FAILOVER=deepseek-v4-flash-anthropicPer-turn model
session.send
may pass
model
(catalog id, alias, or API model name). Empty uses the runtime default. Failover still applies to that resolved primary.
await session.send('Ship the copilot.', {
model: 'deepseek-v4-flash-responses',
})