Skip to content
SVEDA
Menu

CATALOG

A catalog, not a lock-in.

deepseek-v4-flash-responses is the default. Failover walks deepseek-v4-flash-anthropic next. Custom endpoints speak Responses or Anthropic. The stream does not restart.

Get started Models docs

Flash

default catalog id

Anthropic

builtin failover

Pro

same runtime

The problem

Hardcoding a provider SDK in the widget means a new stream parser when the vendor flakes. Failover becomes a UI rewrite. Custom endpoints never join the same ordered list as the builtins. The catalog should live on the runtime.

Model id in the frontend

Shipping deepseek-v4-flash-responses in the Vue tree couples deploy to catalog. The default is on sveda-server. The client may pass model on a turn; it does not own the list.

Failover as a new session

Drop the primary, remount the chat, lose tool state. Sveda walks failover_ids on the same POST /sveda/stream. Event types do not change.

One protocol only

A Responses-only client cannot take an Anthropic URL. Custom entries speak responses or anthropic. Alias deepseek-v4-flash resolves to Flash Responses.

How Sveda does it

Builtin catalog: deepseek-v4-flash-responses is default. Failover walks deepseek-v4-flash-anthropic next. deepseek-v4-pro is in the same list. Custom rows take a URL and protocol responses or anthropic.

Default Flash Responses

Id deepseek-v4-flash-responses. Label DeepSeek V4 Flash (Responses). Alias deepseek-v4-flash maps here.

  • deepseek-v4-flash-responses
  • protocol responses
  • alias deepseek-v4-flash

Ordered failover

Builtin next hop is Flash Anthropic. The stream continues. The client still called session.send once.

  • deepseek-v4-flash-anthropic
  • protocol anthropic
  • same event list on the wire

Pro and custom URLs

deepseek-v4-pro is first-class. Custom endpoints join the catalog with responses or anthropic — not a new client.

  • deepseek-v4-pro
  • custom protocol responses | anthropic
  • failover_ids stay an ordered list
FAILOVER PATH primary live
  • deepseek-v4-flash-responses default
  • deepseek-v4-flash-anthropic failover
  • deepseek-v4-pro catalog

Stream held. Event types unchanged.

Swap a provider. Keep send.

session.send may include model or provider. Failover is still the ordered list on the runtime. You do not rebuild the widget when Flash Responses times out and Flash Anthropic continues the turn.

This is not a hosted model marketplace. Keys and custom URLs stay on sveda-server. The marketing site is not a chatbot SaaS. Point a custom row at any Responses or Anthropic-compatible URL and put it in failover_ids if it should catch a drop.

Ids and env are in the models docs. Model failover is the same catalog, written as a job to keep the stream up.

CATALOG responses | anthropic
  • Flash Responses deepseek-v4-flash
  • Flash Anthropic standby
  • V4 Pro deepseek-v4-pro
  • Custom URL your endpoint

Related

Rust runtime

The catalog is configured on sveda-server, not in @sveda-ai/core.

Stream protocol

Failover does not introduce new event names.

JS client

Optional model on send. Same SvedaClient either way.

Models docs

Catalog ids, protocols, aliases, and failover env.

Model failover

Ordered list without rewriting the stream.

Runtime docs

Where the catalog is served from.

Keep the catalog on the runtime.

Default Flash Responses. Fail over to Flash Anthropic. Add Pro or a custom URL without touching session.send.

Get started