base_url. One LLM object serves any number of agents in the crew.
Install
Connect
The
openai/ prefix selects LiteLLM’s OpenAI-dialect transport; LiteLLM strips it before sending, so Mesh receives auto and routes it. To pin a Mesh catalog id that already contains a slash, the prefix reads as doubled: openai/openai/gpt-4o-mini.A crew with a tool
Caveats
Token counting against auto
CrewAI counts input tokens locally and cannot look up a context window for the literal name auto, so it logs:
Routing varies with prompt size
CrewAI prompts are large: it wraps agent role, goal, backstory, and tool schemas into every call. Withauto that changes which model Mesh selects, so a crew may be served a different model than a bare chat call from the same key. Check the served model rather than assuming.
Everything in Caveats that apply to every framework also applies.
Related
- Agent frameworks — the shared pattern and compatibility matrix
- Auto-routing — how
autopicks a model - Google ADK — the other LiteLLM-based framework