Vercel adds DeepSeek’s latest Flash update to AI Gateway
The new snapshot targets coding and multi-step automation. DeepSeek’s own benchmarks show gains, while Vercel offers a specific model identifier and setup path.
Loading page…
The new snapshot targets coding and multi-step automation. DeepSeek’s own benchmarks show gains, while Vercel offers a specific model identifier and setup path.
Listen to this story
Vercel’s AI Gateway added DeepSeek V4.1 Flash 1017 on Oct. 17, giving developers a selectable snapshot for repository coding, multi-step automation, and tool-assisted image reasoning. DeepSeek reports gains over the prior Flash snapshot on Terminal-Bench 4.0 (31.2 to 42.3), ProgramBench (20.3 to 29.1), and Automation-Bench (54.8 to 60.5); these are vendor benchmarks, and Terminal-Bench used the Claude Code harness. Teams can call the model through Gateway or self-host its MIT-licensed weights. The claimed shorter, faster runs are separate from Gateway’s pass-through pricing and lack of inference platform fees.
The Gateway identifier is `deepseek/deepseek-v4.1-flash-1017`; Vercel documents calling it via `streamText` or configuring Gateway from its CLI.
DeepSeek labels Chartography, BabyVision, and ZeroBench-main as tool-enabled visual tests, so their scores do not establish tool-free image performance.
Self-hosters get MIT-licensed weights and a Python prompt-encoding reference, but no Jinja-format chat template; DeepSeek points to its deepseek-recipe toolkit.
Developers using Vercel’s AI Gateway can now select DeepSeek V4.1 Flash 1017 for coding, image understanding and automated tasks. Vercel announced availability on October 17, describing a minor update with a practical promise: better results from agent runs that finish faster and produce less text than the previous snapshot.
Vercel describes the coding improvements in concrete terms: terminal work, plus building and editing entire code repositories. Its description of better agent performance focuses on multi-step automation—work in which the model carries out a sequence rather than supplying one answer. For images, Vercel points to chart reading and visual reasoning when the model can call tools.
DeepSeek’s model card supplies numerical comparisons with the earlier Flash snapshot. Its reported Terminal-Bench 4.0 score rises from 31.2 to 42.3, while ProgramBench moves from 20.3 to 29.1. Automation-Bench v1.0.6 increases from 54.8 to 60.5. These are DeepSeek’s own benchmark results, not independently verified measures of performance in a customer’s application.
The test setup also matters. DeepSeek says its Terminal-Bench results use the Claude Code harness—the software environment around the model. Its visual table explicitly labels Chartography, BabyVision and ZeroBench-main as tests with tools. The image scores therefore describe tool-enabled evaluations, rather than a claim about image reading without those tools.
DeepSeek reports these scores using the Claude Code harness.
DeepSeek’s comparison shows a higher ProgramBench score for the updated snapshot.
DeepSeek reports an increase on its listed automation benchmark.
The Gateway model identifier is deepseek/deepseek-v4.1-flash-1017. Vercel’s example passes that exact string to streamText from the ai package. For developers working in Claude Code, Codex, Cursor and other tools, Vercel gives another route: install the latest Vercel command-line software, then run its AI Gateway setup command.
npx vercel ai-gateway setupGateway provides a unified interface for calling models, tracking usage and cost, and configuring retries and failover. Vercel also lists budgets for API keys and routing rules. Those are controls around the model request; the announcement presents them as Gateway features, not new capabilities inside DeepSeek’s updated model.
For teams taking the separate route of running the model themselves, DeepSeek’s repository publishes the weights under the MIT license. It does not include a Jinja-format chat template. Instead, DeepSeek provides a Python prompt-encoding reference covering conversations, tool calls, thinking mode and images, plus the deepseek-recipe toolkit for production integrations.
The efficiency claim concerns how much work a task consumes. Vercel says faster completion and shorter outputs mean agent runs tend to take less time and use fewer output tokens—the units used to measure generated text. DeepSeek likewise describes lower task execution time and output length as the basis for completing work at lower cost.
That is distinct from Vercel’s pricing policy for access. The company says AI Gateway passes through provider pricing without markup and charges no platform fee on inference, including requests made with a customer’s own provider key. One claim is about the model doing less generation per task; the other is about the intermediary’s charges.
Loading discussion...
Join the conversation
Explain when less text helps, and when you want more detail.
Be the first to share a perspective or an experience.
Reader comments
Newest comments first. Replies stay oldest first.