Skip to main content

Overview

CrewAI supports two paths for connecting to LLM providers:
  1. Native integrations — direct SDK connections to OpenAI, Anthropic, Google Gemini, Azure OpenAI, and AWS Bedrock
  2. LiteLLM fallback — a translation layer that supports 100+ additional providers
This guide explains how to use CrewAI exclusively with native provider integrations, removing any dependency on LiteLLM.
The litellm package was quarantined on PyPI due to a security/reliability incident. If you rely on LiteLLM-dependent providers, you should migrate to native integrations. CrewAI’s native integrations give you full functionality without LiteLLM.

Why Remove LiteLLM?

  • Reduced dependency surface — fewer packages means fewer potential supply-chain risks
  • Better performance — native SDKs communicate directly with provider APIs, eliminating a translation layer
  • Simpler debugging — one less abstraction layer between your code and the provider
  • Smaller install footprint — LiteLLM brings in many transitive dependencies

Native Providers (No LiteLLM Required)

These providers use their own SDKs and work without LiteLLM installed:

OpenAI

GPT-4o, GPT-4o-mini, o1, o3-mini, and more.

Anthropic

Claude Sonnet, Claude Haiku, and more.

Google Gemini

Gemini 2.0 Flash, Gemini 2.0 Pro, and more.

Azure OpenAI

Azure-hosted OpenAI models.

AWS Bedrock

Claude, Llama, Titan, and more via AWS.
If you only use native providers, you never need to install crewai[litellm]. The base crewai package plus your chosen provider extra is all you need.

How to Check If You’re Using LiteLLM

Check your model strings

If your code uses model prefixes like these, you’re routing through LiteLLM:

Check if LiteLLM is installed

If the command returns package information, LiteLLM is installed in your environment.

Check your dependencies

Look at your pyproject.toml for crewai[litellm]:

Migration Guide

Step 1: Identify your current provider

Find all LLM() calls and model strings in your code:

Step 2: Switch to a native provider

Step 3: Keep Ollama without LiteLLM

If you’re using Ollama and want to keep using it, you can connect via Ollama’s OpenAI-compatible API:
Many local inference servers (Ollama, vLLM, LM Studio, llama.cpp) expose an OpenAI-compatible API. You can use the openai/ prefix with a custom base_url to connect to any of them natively.

Step 4: Update your YAML configs

Step 5: Remove LiteLLM

Once you’ve migrated all your model references:

Step 6: Verify

Run your project and confirm everything works:

Quick Reference: Model String Mapping

Here are common migration paths from LiteLLM-dependent providers to native ones:

FAQ

No, if you use one of the five natively supported providers (OpenAI, Anthropic, Gemini, Azure, Bedrock). These native integrations support all CrewAI features including streaming, tool calling, structured output, and more. You only lose access to providers that are exclusively available through LiteLLM (like Groq, Together AI, Mistral as first-class providers).
Yes. Install multiple extras and use different providers for different agents:
Regardless of quarantine status, reducing your dependency surface is good security practice. If you only need providers that CrewAI supports natively, there’s no reason to keep LiteLLM installed.
Native providers use the same environment variables you’re already familiar with. No changes needed for OPENAI_API_KEY, ANTHROPIC_API_KEY, GEMINI_API_KEY, etc.