feat(inference): update custom models

Author: fpagny

pages/managed-inference/reference-content/supported-models.mdx

@@ -58,8 +58,37 @@ The model files need to include:
   - `tokenizer_config.json` file as `chat_template` field
   - `chat_template.json` file as `chat_template` field
 
+The model type need to either be:
+- `chat`
+- `vision`
+- `multimodal` (`chat` and `vision` currently)
+- `embedding`
+
 For security reasons, models containing arbitrary code execution such as [`pickle`](https://docs.python.org/3/library/pickle.html) format are not supported. 
 
+### Supported API
+
+Depending on the model type, specific endpoints and features will be supported.
+
+#### Chat models
+
+Chat API will be expposed for this model under `/v1/chat/completions` endpoint.
+**Structured outputs** or **Function calling** are not yet supported for custom models.
+
+#### Vision models
+
+Chat API will be expposed for this model under `/v1/chat/completions` endpoint.
+**Structured outputs** or **Function calling** are not yet supported for custom models.
+
+#### Multimodal models (vision and chat)
+
+These models will be treated similarly to both Chat and Vision models.
+
+#### Embedding models
+
+Embeddings API will be exposed for this model under `/v1/embeddings` endpoint.
+
+
 ### Custom model lifecycle
 
 Currently, custom model deployments are considered to be valid for a long term, and we will ensure any updatse or changes to Managed Inference will not impact existing deployments.