DeepSeek V4.1 Flash GA supports Responses and Chat Completions with text and image understanding.
Provider: DeepSeek
Category: text generation
Endpoint: /v1/responses
Status: Available
Cost: --
deepseek-v4.1-flash
DeepSeek V4.1 Flash GA supports Responses and Chat Completions with text and image understanding.
API access
Endpoint
POST /v1/responses
Base URL
https://api.hiapi.ai
Uses the OpenAI Responses format. One HiAPI key works across all available models.
Input price
880 Credits
/ 1M tokens
Output price
2,640 Credits
/ 1M tokens
Context
1M
context window
Max output
384K
output tokens
Try deepseek-v4.1-flash
Ask a question, upload images, or paste from clipboard. Then inspect the streamed answer, token usage, latency, and estimated cost.
Upload or paste up to 4 images, 10 MB each. Images are safety reviewed.
deepseek-v4.1-flash API Quickstart
Call deepseek-v4.1-flash with the streaming OpenAI Responses format. Copy a ready-to-use cURL, Python, or Node.js example below.
/v1/responsescurl -N -X POST "https://api.hiapi.ai/v1/responses" \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "deepseek-v4.1-flash",
"input": [
{
"type": "message",
"role": "user",
"content": [
{
"type": "input_text",
"text": "用三句话解释 API 缓存的作用。"
}
]
}
],
"stream": true,
"max_output_tokens": 1024
}'Tip: Replace YOUR_API_KEY with your actual API key from the API Keys page.
Uses the OpenAI Responses format. Keep stream: true, send input as a message array, and set reasoning effort with reasoning.effort.
The example defaults to reasoning.effort=high. Use max for maximum effort or none to disable reasoning.
Combine input_text and input_image in one input message. Use a public HTTPS image URL; Playground uploads automatically provide a temporary reviewed URL.
/v1/responsescurl -N -X POST "https://api.hiapi.ai/v1/responses" \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"model": "deepseek-v4.1-flash",
"input": [
{
"type": "message",
"role": "user",
"content": [
{
"type": "input_text",
"text": "Describe the main subject, setting, and important visual details."
},
{
"type": "input_image",
"image_url": "https://static.hiapi.ai/example/subject-1.jpg",
"detail": "low"
}
]
}
],
"stream": true,
"max_output_tokens": 1024,
"reasoning": {
"effort": "high"
}
}'Tip: Replace YOUR_API_KEY with your actual API key from the API Keys page.
Uses the OpenAI Responses format. Keep stream: true, send input as a message array, and set reasoning effort with reasoning.effort.
The example defaults to reasoning.effort=high. Use max for maximum effort or none to disable reasoning.
Responses API
Request fields at a glance
Start with core fields, then enable advanced capabilities as needed.
Core fields
The fields that form a valid request
- model Required
- Use deepseek-v4.1-flash.
- input Required
- Send a message array or text input.
- stream Optional
- Supports streaming and non-streaming responses; examples use true.
- instructions Optional
- Define the model role and response requirements.
Capability fields
Set verified reasoning effort and output limits
- reasoning.effort Optional
- Supports none, low, high, and max; defaults to high. none disables reasoning.
- max_output_tokens Optional
- Limit the maximum output tokens for this response.
- State and storage Optional
- This endpoint is stateless; omit store, previous_response_id, and conversation.
DeepSeek Responses is stateless and does not support previous_response_id or conversation. Replay required context in the next input and omit store.
deepseek-v4.1-flash API Pricing
Billing follows the input, output, and cache token categories actually reported in usage. All prices below are shown per 1 million tokens.
- Input tokens
- 880 Credits/ 1M tokens
- Output tokens
- 2,640 Credits/ 1M tokens
Prompts and context sent to the model
Responses generated by the model
- Cache read
- 28 Credits/ 1M tokens
deepseek-v4.1-flash Model Specifications
These specifications reflect the current public HiAPI text request contract. Undisclosed capabilities are not inferred by the page.
- Streaming
- Supported
- Tool calling
- Not supported
- Structured JSON
- Not supported
- Reasoning
- Not supported
- Input modalities
- text · image
- Output modalities
- text
- Reasoning efforts
- -
- Max output
- 384K
About deepseek-v4.1-flash
DeepSeek V4.1 Flash GA supports Responses and Chat Completions with text and image understanding.
HiAPI exposes this model through /v1/responses. Test prompts and parameters in the Playground, then use the same HiAPI API key in your server application.
- Provider
- DeepSeek
- Endpoint
- /v1/responses
- Context window
- 1M
- Released
- 2026-09-10
How to Use deepseek-v4.1-flash
The Playground and API share the same model ID, so three steps take a prompt into production.
Step 1
Validate online
Test instructions, input, and reasoning.effort in the Playground.
Step 2
Manage API keys
View an existing key or create another after signing in; one key works across all available models.
Step 3
Integrate your server
Send requests to /v1/responses and track cost with the usage object.
Frequently asked questions
How do the official name and the HiAPI model ID differ?
DeepSeek's official model name is deepseek-flash. HiAPI's public model ID for this integration remains deepseek-v4.1-flash. Continue using deepseek-v4.1-flash in requests and examples.
What is DeepSeek V4.1 Flash?
DeepSeek V4.1 Flash is a production model for text and image input. According to DeepSeek's official documentation, it supports a 1M-token context window, up to 384K output tokens, and none, low, high, and max reasoning efforts, with high as the default.
Which model ID and endpoint should I use?
Set model to deepseek-v4.1-flash. Use POST /v1/responses or the compatible POST /v1/chat/completions endpoint. Responses uses input; Chat Completions uses messages. Do not mix their request shapes.
How do I enable or disable reasoning?
Responses uses reasoning.effort: none disables reasoning; low, high, and max enable it, with high as the default. Chat Completions uses thinking.type=enabled/disabled with reasoning_effort=low, high, or max when enabled.
How do multi-turn Responses conversations work?
This endpoint is stateless. Send the required conversation history in input on every request. Do not send previous_response_id, conversation, background, or context_management, and omit store.
How does a streamed response end?
Read text increments from response.output_text.delta and final usage from response.completed. response.incomplete and response.failed indicate incomplete generation and failure. Responses does not end with [DONE]; Chat Completions streams still use [DONE].
How are tokens and reasoning billed?
Input, output, and cached input tokens are billed separately. Reasoning tokens count as output. Check usage.input_tokens, usage.output_tokens, and input_tokens_details.cached_tokens against the API log. Refer to the live pricing section for current rates.
Are image input, tool calls, and structured JSON enabled?
DeepSeek's official documentation supports image URLs and base64 image input. Tool calls and structured JSON are not advertised for this integration.
Can I reuse an existing HiAPI API key?
Yes, if it has access to the model and available balance. With the OpenAI SDK, set base_url to https://api.hiapi.ai/v1. Use client.responses.create for Responses or client.chat.completions.create for Chat Completions.
HiAPI Blog
