CHINZY / MODEL API
DeepSeek V4 Pro
Review an engineering change against its original requirement and acceptance criteria. Ask for missing evidence item by item and rerun the same sample after changing a revision.
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-V4-Pro | text | 1,048,576 / Not listed | Not listed |
qwen/vanchin/deepseek-v4-pro | text | Not listed / Not listed | Not listed |
qwen/vanchin/deepseek-v4-pro-0813 | 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-V4-Pro",
"messages": [
{
"role": "user",
"content": "Requirement: export CSV and JSON. Test record: CSV passed. What evidence is missing?"
}
]
}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)
{
"missing_evidence": "JSON export test"
}