Slot definitions and object rules

The old handler comment stating 11 entries is outdated and does not establish the count. Read back from the actual deployment; this table is not production configuration.

slot_id

Name

frontend_behavior

Allowed model types

parse

Document parse

hidden

chat_multimodal, ocr

audio_parse

Audio parse

hidden

asr

extract

Information extract

hidden

chat_text, chat_multimodal

img_parse

Image parse

hidden

chat_multimodal, ocr

ai_infer

AI inference

selectable

chat_text, chat_multimodal

embed_text

Text embedding

hidden

embedding_text

embed_img

Image embedding

hidden

embedding_multimodal, embedding_text

rerank

Rerank

hidden

rerank_text, rerank_multimodal

workflow

Intelligent workflow

selectable

chat_text, chat_multimodal

nl2sql

NL2SQL

hidden

chat_text, chat_multimodal

knowledge_qa

Knowledge Q&A and RAG

selectable

chat_text, chat_multimodal

agent_chat

Agent chat

selectable

chat_text, chat_multimodal

hidden describes frontend selection only, not whether a feature is disabled. configured means only that the allowlist is nonempty. Existing configuration may retain configured=true when the candidate catalog is empty; this does not establish that the model is callable or routing is healthy.

Model IDs are trimmed and empty entries removed before checking duplicates. Duplicates are rejected rather than deduplicated. Every item in a nonempty list is checked for catalog existence and allowed type. An empty default_model_id selects the first item. An explicit default moves to the front while other items retain their relative order. models[].position starts at 0 in the resulting order.

List reads supplement models[].type from the catalog. Write responses project the saved configuration and may currently return an empty type. Default and model names currently use model IDs; do not assume provider display names. Lists always return a models array. Unconfigured default_model_id is an empty string; empty default_model_name and extra_json may be omitted.

Logs expose summary fields only. Although an internal table stores before/after JSON, the response does not include those fields. page_size limits only the most recent window; a full page does not imply that another page can be requested. Do not construct recovery or cursor APIs from unexposed fields.

Last updated on