What changed
LiteLLM v1.91.0 landed on July 4 with a cluster of product-facing updates instead of a single bug fix. The release adds an Interactions API endpoint to the playground with SSE streaming, migrates LiteLLM to Google's newer Interactions API steps schema, adds Gemini managed agents support, and enables native MCP OAuth support for Cursor.
A day later, LiteLLM v1.92.0-rc.1 extended the same direction with more production-ready MCP token exchange work and Prometheus metrics labeled by API provider. That makes the story bigger than one release: LiteLLM is steadily moving from model proxy to a control layer for agent traffic, authentication, and observability.
For context on the provider-side shift, Google's Interactions API documentation shows the newer agent-oriented request model that gateway vendors now need to absorb quickly.
Why it matters
This is a useful product signal for builders because it compresses three kinds of platform work into one place.
First, provider APIs are changing fast. Supporting Google's newer interaction schema and managed-agent features means teams can keep one gateway in front of multiple model backends instead of rewriting every app surface when a provider evolves its agent interface.
Second, agent products are pulling identity and tool access into the platform layer. Native MCP OAuth support for Cursor and stronger MCP token-exchange work suggest that gateway software is becoming the place where external tools, users, and policies get stitched together.
Third, the release keeps adding operational detail, not just feature checkboxes. Provider-labeled Prometheus metrics are exactly the kind of small improvement that matters when teams need to debug latency, cost, or reliability across multiple model vendors.
The takeaway
The interesting angle is not just that LiteLLM shipped another release. It is that gateway products are becoming the compatibility and governance layer for agent systems. If you are building AI features into a product, that layer increasingly decides how painful provider changes, tool auth, and multi-model operations will be.