DeepSeek V4.1 Flash 1017
DeepSeek · OpenAI-compatible API
deepseek/deepseek-v4.1-flash-1017USD / 1M tokens
- Context
- 1M
- Max Output
- 384K
- Tool Calling
- ✓
- Reasoning
- ✓
- Vision
- ✓
- Streaming
- ✓
Official specifications list image input for Flash 1017. This Gateway route returned HTTP 400 (unsupported_image_input); use text input here. Official Responses, search and fetch features were not tested on this route.
import os
from openai import OpenAI
client = OpenAI(
base_url="https://api.iteracompute.com/v1",
api_key=os.environ["ITERACOMPUTE_API_KEY"],
)
response = client.chat.completions.create(
model="deepseek/deepseek-v4.1-flash-1017",
messages=[{"role": "user", "content": "Hello!"}],
)
print(response.choices[0].message.content)import OpenAI from "openai";
const client = new OpenAI({
baseURL: "https://api.iteracompute.com/v1",
apiKey: process.env.ITERACOMPUTE_API_KEY,
});
const response = await client.chat.completions.create({
model: "deepseek/deepseek-v4.1-flash-1017",
messages: [{ role: "user", content: "Hello!" }],
});
console.log(response.choices[0].message.content);curl https://api.iteracompute.com/v1/chat/completions \
-H "Authorization: Bearer $ITERACOMPUTE_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "deepseek/deepseek-v4.1-flash-1017",
"messages": [{"role": "user", "content": "Hello!"}]
}'Catalog updated: 2026-10-21.
Overview
October 17 release for coding and text workflows: 1M context, 384K maximum output. Streaming, reasoning, JSON and tool calls verified; image input is unavailable on this route.
Official model specifications
- Context
- 1M
- Max Output
- 384K
- Tool calling
- Supported
- Reasoning
- Supported
- Image input
- Supported
- Streaming
- Supported
Capabilities and full context are from provider documentation. Gateway request limits and feature availability can differ.
Model developer documentation ·
Official specifications list image input for Flash 1017. This Gateway route returned HTTP 400 (unsupported_image_input); use text input here. Official Responses, search and fetch features were not tested on this route.
Gateway request limits
- Input limit
- 1M
- Output limit
- 384K
A missing Gateway limit is unpublished, not unlimited. Provider capabilities are not a route acceptance test.
Tasks and selection tradeoffs
Use for focused code changes, document extraction and bounded tool workflows. Review generated patches and validate JSON in your application.
Choose your tool
Route acceptance record
Short checks passed with default reasoning and max_tokens=512 plus max_completion_tokens=512. Streaming included final usage and [DONE]; the tool check included returning a tool result and a final answer. These checks do not validate a full coding agent or the complete 1M context.
Official specifications list image input for Flash 1017. This Gateway route returned HTTP 400 (unsupported_image_input); use text input here. Official Responses, search and fetch features were not tested on this route.
| Test date | Endpoint | Capability | Route test |
|---|---|---|---|
POST /v1/chat/completions | Text response | Passed | |
POST /v1/chat/completions | Reasoning | Passed | |
POST /v1/chat/completions | Streaming | Passed | |
POST /v1/chat/completions | JSON mode (json_object) | Passed | |
POST /v1/chat/completions | Tool calling | Passed | |
POST /v1/chat/completions | Image input | Check failed |
Small acceptance samples on the stated date. Full context and output limits are catalog declarations; long-context quality, complete coding workflows and sustained stability were not established by these checks.
Pricing
Prices in USD per 1M tokens.
Example task: Extract fields from a document
Assume 12,000 aggregate input tokens and 1,000 billable output tokens across all calls. No cache hit.
12,000 × $0.17 / 1M + 1,000 × $0.7 / 1M = $0.002740
If usage actually reports 9,000 of those input tokens as cached, replace that portion at the cached-input rate ($0.005/1M): $0.001255. Cached tokens are part of total input, never added on top.
Illustrative calculation using the 2026-10-21 catalog snapshot. Include every agent call and retry, repeated history and billable reasoning output; settle against actual usage and current Console prices.
Estimate your monthly cost
Uses the 2026-10-21 catalog snapshot, independently of the live prices above. USD per 1M tokens; an estimate, not a bill.
Estimate includes standard text input, cache reads and text output only. Long-context premiums, service tiers, cache writes, image output and tool fees are excluded.
Cache-hit share = cache-hit tokens ÷ total input. Changing total input keeps the current share; dragging the slider updates cache-hit tokens. Output includes billable reasoning. Count agent steps and retries as requests.
Estimated monthly cost
—USD / monthDeepSeek V4.1 Flash 1017
- Uncached input
- —
- Cache read
- —
- Billable output
- —
Calculation and billing basis
Monthly cost = requests × [input × (1 − cached share) × input rate + input × cached share × cache-read rate + output × output rate] / 1,000,000.
Cached tokens are part of total input, never added on top. Use actual cache-read hits from usage; repeating a prompt does not guarantee a hit. Missing rates are unconfirmed, not $0. Separate cache-write, storage and other additional fees are excluded. Settle against actual usage and current Console prices.
Usage limits
- Use the Gateway request limits above when configuring clients. Official context describes the model capacity, not an account entitlement.
- Start with one representative task. Check correctness, actual usage and response time before increasing traffic.
API parameters
| Parameter / protocol field | Usage |
|---|---|
model / messages | Use the exact model ID and chat message list |
tools / tool_calls / tool messages | Use tools to define functions and role=tool to return their results |
stream / stream_options.include_usage | Use SSE streaming with final usage |
max_tokens | Set an output budget within the model and account limits |
Parameters vary by model. Keep model-specific controls separate from shared OpenAI-compatible fields.
API
- Base URL
https://api.iteracompute.com/v1- Endpoint
POST /v1/chat/completions- Model ID
deepseek/deepseek-v4.1-flash-1017- Authentication
Authorization: Bearer ITERACOMPUTE_API_KEY
FAQ
How do I use DeepSeek V4.1 Flash 1017 with the OpenAI SDK?
Set base_url to https://api.iteracompute.com/v1 and model to deepseek/deepseek-v4.1-flash-1017. Authenticate with your IteraCompute API key.
What does DeepSeek V4.1 Flash 1017 cost?
See the pricing section for current input, cached-input and output rates in USD per 1M tokens. Check the refresh time before use.
What context length is available?
See the model specifications above for the current context and maximum output. Input and requested maximum output share the context budget.
Ready for your first request?
Create your key, choose a tool and get a non-empty first reply.