Skip to main content
CrewAI routes model calls through LiteLLM, so Mesh is reached with LiteLLM’s OpenAI-dialect transport and an explicit 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:
This is CrewAI’s own bookkeeping only — Mesh bills and logs usage against the real served model. Pin a catalog id if you need CrewAI’s own counts to be exact.

Routing varies with prompt size

CrewAI prompts are large: it wraps agent role, goal, backstory, and tool schemas into every call. With auto 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.