reproduction: AI Gateway DeepSeek V3.2 metadata appears stale/inconsistent

[lgrammel]

Bug

AI Gateway DeepSeek V3.2 metadata appears stale/inconsistent

Reproduction

• Expected AI Gateway catalog metadata, per-provider endpoint metadata, and rendered model pages to agree on provider source, pricing source, and output limits for the DeepSeek V3.2 IDs.
• Observed live metadata for deepseek/deepseek-v3.2-thinking remains inconsistent: the rendered page says the Thinking variant is available under the deepseek provider, but /v1/models/deepseek/deepseek-v3.2-thinking/endpoints lists only bedrock, deepinfra, fireworks, and novita.
• Observed /v1/models aggregate pricing for deepseek/deepseek-v3.2-thinking is still Bedrock-like $0.62/M input and $1.85/M output, but the model object does not expose Bedrock or any other provider as the aggregate pricing source.
• Observed /v1/models reports max_tokens: 8000 for deepseek/deepseek-v3.2-thinking, while the rendered page says it generates up to 163K tokens and has a 163K output token budget.
• The exact originally reported deepseek provider endpoint row for deepseek/deepseek-v3.2-thinking is no longer present, but the primary stale/inconsistent Gateway catalog and page metadata behavior is still reproducible.
• Added runnable live reproduction script at examples/ai-functions/src/reproduction/issue-15894-ai-gateway-deepseek-v32-metadata.ts.
• Recorded live Gateway/page evidence in packages/gateway/src/__fixtures__/issue-15894-deepseek-v3.2-catalog.json and added failing fixture-based regression test at packages/gateway/src/issue-15894-deepseek-v32-catalog-metadata.test.ts.

Relevant Documentation

• https://api-docs.deepseek.com/
• https://api-docs.deepseek.com/news/news260424/
• https://vercel.com/docs/ai-gateway/models-and-providers
• https://vercel.com/ai-gateway/models/deepseek-v3.2
• https://vercel.com/ai-gateway/models/deepseek-v3.2-thinking

Related Issues

Reproduces #15894