CHINZY / MODEL API
DeepSeek V3.2
Extract ticket fields with fixed keys and validate the JSON with a parser. Use identical inputs across routes, then check field values separately from syntax.
Reviewed text API routes
This is a catalog snapshot. A model’s upstream capabilities may differ from the interface exposed here. Check the alias and current price in the live catalog first. Limits are not measured throughput or latency.
Catalog sync / review date: 2026-10-09 /
| Request alias | Catalog input types | Context / max output (tokens) | Request requirements |
|---|---|---|---|
siliconflow/deepseek-ai/DeepSeek-V3.2 | text | 163,840 / Not listed | Not listed |
siliconflow/Pro/deepseek-ai/DeepSeek-V3.2 | text | 163,840 / Not listed | Not listed |
qwen/siliconflow/deepseek-v3.2 | text | Not listed / Not listed | Not listed |
Minimal API example
Confirm the alias is still active. Save the example JSON as request.json and set CHINZY_API_KEY on your server before running the command. The sample uses fictional data.
{
"model": "siliconflow/deepseek-ai/DeepSeek-V3.2",
"messages": [
{
"role": "user",
"content": "Ticket 134: pump P2, missing gasket. Return JSON with id, asset and issue."
}
]
}curl https://chinzy.com/v1/chat/completions \
-H "Authorization: Bearer $CHINZY_API_KEY" \
-H "Content-Type: application/json" \
--data-binary @request.jsonFacts to check (illustration, not a measured response; format may vary)
{
"id": 134,
"asset": "P2",
"issue": "missing gasket"
}