various fixes for guardrail on openrouter models and an new guardrail option

[Reapor-Yurnero]

various fixes for guardrail on openrouter models and an new guardrail option

Pre-Submission checklist

Please complete all items before asking a LiteLLM maintainer to review your PR

• I have Added testing in the tests/litellm/ directory, Adding at least 1 test is a hard requirement - see details
• My PR passes all unit tests on make test-unit
• My PR's scope is as isolated as possible, it only solves 1 specific problem

CI (LiteLLM team)

CI status guideline:

• 50-55 passing tests: main is stable with minor issues.
• 45-49 passing tests: acceptable but needs attention
• <= 40 passing tests: unstable; be careful with your merges and assess the risk.

• Branch creation CI run
  Link:

• CI run for the last commit
  Link:

• Merge / cherry-pick CI run
  Links:

Type

🐛 Bug Fix

Changes

1. fix various issues in the new generic interface when /messages is used against an openrouter model
2. also adding missed exception handling in /response API for the exception introduced recently
3. add an option so that only when all chunks are collected a single request is going to be sent to the guardrail

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Review	Updated (UTC)
litellm	Ready	Preview, Comment	Dec 17, 2025 0:49am