Models/DeepSeek V4.1 Flash 1017
Chat · Alibaba Cloud Model Studio

DeepSeek V4.1 Flash 1017 API

DeepSeek V4.1 Flash 1017 is the dated 1017 build of V4.1 Flash. DeepSeek's release notes describe a 552B-parameter MoE with 8B input / 16B output activation, native multimodal input, smaller KV cache and released open weights. Use the dated ID when you need to pin this build.

Context 1.024MMax output —From ¥0.5 / ¥2 input/output

Official source: model page · verified 2026-10-22

PRICING

Pricing

CNY / usage-based
TierInput / 1MCached / 1MOutput / 1M
Off-peak¥0.5¥0.05¥2
Peak¥1¥0.1¥4

Prices can change with upstream providers; the rate at settlement is authoritative.

QUICKSTART

Call the API

Use the OpenAI-compatible endpoint; no model-specific SDK setup is required.

Shell
curl https://api.kimiseek.app/v1/chat/completions \
  -H "Authorization: Bearer $KIMISEEK_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "deepseek-v4.1-flash-1017",
    "messages": [{"role": "user", "content": "Hello from KimiSeek"}]
  }'
FIT

Where it fits

Best for

  • Reproducible V4.1 Flash deployments
  • Cost-sensitive agent and coding workloads
  • Teams that need a pinned current DeepSeek build

Tradeoffs

  • A dated snapshot will not automatically receive later improvements
  • The rolling deepseek-v4.1-flash entry is the general alias; compare both before pinning
DETAILS

Model details

One API keyCNY billingOpenAI-compatiblePay as you go

FAQ

What is the difference from deepseek-v4.1-flash?

This is the 1017 dated build. The rolling alias points at the current V4.1 Flash configuration; use this ID when reproducibility matters.

Is this model open source?

DeepSeek publishes weight links for V4.1 Flash 1017. Review the current Hugging Face or ModelScope licence before self-hosting.

How do I call this model?

Use KimiSeek's OpenAI-compatible API and set the model field to deepseek-v4.1-flash-1017 with your KimiSeek API key.