# DeepSeek V4 Pro now runs updated weights on AI Gateway

Source: [Vercel](https://vercel.com/changelog/deepseek-v4-pro-now-runs-updated-weights-on-ai-gateway)  
Feed7 permalink: https://feed7.dev/p/deepseek-v4-pro-now-runs-updated-weights-on-ai-gateway-0unky4f  
Published: 2026-08-12T07:00:00.000Z  
Trust: Official Source (official_source)

## Why Included

AI Gateway moved DeepSeek V4 Pro’s existing alias to updated weights without a code change. Pinning is documented inconsistently, so verify the dated model ID first.

## Source Summary

Calls to **deepseek/deepseek-v4-pro** now receive updated weights by default on AI Gateway, with no application change. The post also offers a dated ID for explicitly selecting the revision in AI SDK or coding-agent configuration.

## Practical Implication

Existing users should rerun representative agent tasks because an unchanged alias can now produce different behavior. Pin a dated revision when reproducibility matters, and use the gateway’s coding-agent setup when routing a local agent through it.

## Agent-Ready Context

Calls to **deepseek/deepseek-v4-pro** now receive updated weights by default on AI Gateway, with no application change. The post also offers a dated ID for explicitly selecting the revision in AI SDK or coding-agent configuration.

Existing users should rerun representative agent tasks because an unchanged alias can now produce different behavior. Pin a dated revision when reproducibility matters, and use the gateway’s coding-agent setup when routing a local agent through it.

The material conflicts on the pinned slug: its prose names **deepseek-v4-pro-0813**, while the code sample uses **deepseek-v4-pro-0831**. Confirm the valid identifier before changing production or evaluation configurations.

## Connected Context

Feed7 judgment across 479 accumulated Signals:

This confirms that a stable gateway alias does not guarantee stable model behavior: representative agent evaluations should rerun when weights change, while dated IDs become necessary for reproducibility. The contradictory pinned slugs add a configuration-integrity risk, so neither production pinning nor benchmark attribution is safe until the valid revision ID is verified.

- [DeepSeek V4 Flash now runs updated weights on AI Gateway](https://feed7.dev/p/deepseek-v4-flash-now-runs-updated-weights-on-ai-gateway-1qqe8mw) — Both replace weights behind an unchanged DeepSeek alias, reinforcing continuous workload evaluation and explicit revision pinning when behavior must remain reproducible.
- [Ling 3.0 Tiny is now available on AI Gateway](https://feed7.dev/p/ling-3-0-tiny-is-now-available-on-ai-gateway-1v4j94m) — Ling’s scheduled model-ID transition likewise shows that model selection includes configuration lifecycle management, though this signal adds the sharper risk of conflicting documented revision IDs.

## Context Map

- Layer: model
- Domains: coding
- Topics: model-selection, coding-agents

## Uncertainty

- The material conflicts on the pinned slug: its prose names **deepseek-v4-pro-0813**, while the code sample uses **deepseek-v4-pro-0831**. Confirm the valid identifier before changing production or evaluation configurations.

## Agent Instruction

Use this item as source-backed context. Do not invent claims beyond the linked source. If this item conflicts with another source, call out the conflict.