Skip to main content
CrewAI talks to LLMs through LiteLLM. Point its LLM at the Orbitrage gateway and every agent’s call is routed and traced.

Install

Setup

Model names: CrewAI/LiteLLM validate the model id client-side against their registry, so recognized OpenAI names pass validation out of the boxopenai/gpt-oss-20b, openai/gpt-4o, openai/gpt-4.1. The gateway serves them and traces everything. Note that gpt-4o/gpt-4.1 are closed frontier models and need your own OpenAI key (BYOK); gpt-oss-20b is open-weight and billed to credits.Ids LiteLLM doesn’t recognize — openai/minimax-m3, openai/glm-5.2, or openai/auto are rejected by LiteLLM before the call is made. To use them, register the model with LiteLLM first:

Managed tools (server-side, no keys)

CrewAI agents use CrewAI-native tools, but you can call managed tools directly through the LLM with llm.call(...) — Orbitrage runs them server-side and returns the final answer.
CrewAI’s LLM doesn’t forward custom headers, so per-request user_id switching isn’t available through it — the user_id you pass to orbitrage.init() attributes the whole crew’s run.