docs(passthrough): managed ids cover streamed responses and use the real passthrough prefix

[mateo-berri]

Companion to BerriAI/litellm#38320 (passthrough managed ids for streamed responses)

The page previously used /openai/v1/files and /openai/v1/batches as its example routes. On a live proxy those paths are served by the unified native endpoints, which are matched before the generic passthrough router, so passthrough_managed_object_ids never sees them and a user following the docs got no protection and no error. Every example now uses the real passthrough prefixes (/openai_passthrough/..., /azure/openai/...) and an admonition spells out that the three /openai/v1/* object routes are native endpoints with their own controls

Also documents what the linked PR adds and what stays out of scope: streamed POST /v1/responses is now owned and rewritten from the first response.created event; objects the proxy never saw (created before the flag, or provider-direct) stay unowned, with one custom passthrough endpoint per team carrying that team's own provider key as the strict isolation option; raw provider ids that map to another caller's resource are refused with 404

---

Note

Low Risk
Documentation-only changes with no runtime or security behavior modified in this PR.

Overview
Updates Passthrough Managed IDs documentation so examples match real proxy routing and reflect behavior from the companion implementation PR.

Route corrections: All OpenAI passthrough examples now use /openai_passthrough/... instead of /openai/v1/..., with an info callout explaining that /openai/v1/files, /openai/v1/batches, and /openai/v1/responses are native routes (use require_managed_files or Responses ownership there, not passthrough managed IDs).

Streaming: The comparison table and limitations now state that POST /v1/responses with stream: true rewrites response.id from the first response.created event through the stream; other SSE passthrough streams are still relayed unchanged.

Ownership edge cases: New section on objects the proxy never recorded (pre-flag or provider-direct), plus per-team custom passthrough endpoints with separate provider keys as the strict isolation pattern. Raw provider IDs are documented as owner-checked when mapped to a managed resource (404 for another tenant’s ID); unrecorded raw IDs still pass through.

^{Reviewed by Cursor Bugbot for commit 39b00b7. Bugbot is set up for automated code reviews on this repo. Configure here.}

[mateo-berri]

bugbot run

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
litellm	Ready	Preview	Aug 26, 2026 8:15am

[cursor]

✅ Bugbot reviewed your changes and found no new issues!

Comment @cursor review or bugbot run to trigger another review on this PR

^{Reviewed by Cursor Bugbot for commit 39b00b7. Configure here.}