Text Generation Models
SilvaMux supports multiple vendor-protocol compatible entries plus an optional unified entry. New projects should integrate via the vendor protocol their target model supports; projects using the OpenAI SDK should default to the OpenAI Chat Completions compatible entry.
Vendor Protocol Compatible Entries (Recommended)
The endpoints below accept the corresponding vendor's request format and preserve the matching response and error structures — ideal for official SDKs, existing code migration, or field-level pass-through.
| Compatible format | Endpoint | Docs |
|---|---|---|
| OpenAI Chat Completions | POST /api/v1/chat/completions | OpenAI Compatible API |
| Anthropic | POST /api/v1/messages | Anthropic Compatible |
| Volcengine v3 | POST /api/v3/chat/completions | Volcengine Compatible |
| Zhipu | POST /api/paas/v4/chat/completions | Zhipu Compatible |
| SilvaMux unified entry | POST /api/v0/chat/completions | SilvaMux Unified Entry |
| Responses | POST /api/v1/responses | Compatible with the OpenAI Responses API; for supported models (e.g. the codex series) |
| Gemini | POST /api/v1beta/models/{model}:generateContent | Compatible with the Gemini generateContent format; no publicly discoverable models currently, so no executable example |
These paths are SilvaMux compatible entries, not the vendors' official service addresses. Calls use SilvaMux-issued API keys. The public OpenAPI treats the standard paths above as the contract for new integrations; the historical addresses /api/anthropic/v1/messages and /api/v1/gemini/v1beta/models/{model}:generateContent remain only for existing projects and should not be used by new ones.
OpenAI Responses
Compatible with the OpenAI Responses API; for supported models (e.g. the codex series):
Common Parameters
Common parameters for OpenAI Chat and the unified entry:
| Parameter | Type | Description |
|---|---|---|
model | string | Required. Model call name (id or alias), e.g. minimax-m2.5, doubao-seed-2.0-pro |
messages | array | Required. Message list, same shape as OpenAI (role + content) |
stream | boolean | Whether to stream the response; default false |
temperature | number | Sampling temperature; default 1.0 |
max_tokens | integer | Maximum generated tokens |
Field structures differ per vendor protocol. First filter the Model Plaza for models supporting your target format, then copy the call name from the detail page into
model.
Authentication
Authorization: Bearer <API_KEY> or x-api-key: <API_KEY>.
Streaming
Set stream: true to get a streaming response (SSE). The response is text/event-stream, each event starting with data: . You may eventually receive a usage chunk with an empty choices, after which the server closes the connection; do not rely solely on data: [DONE] to detect completion. Anthropic-format streaming follows the Anthropic SSE specification.
curl https://www.silvamux.com/api/v1/chat/completions \
-H "Authorization: Bearer $SILVAMUX_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "minimax-m2.5",
"messages": [{"role": "user", "content": "Write a short poem"}],
"stream": true
}'
Multimodal
For image, audio, and other multimodal input formats, see Multimodal Input.