llm parameter - all providers use the same unified API.
Supported Providers (60+)
Core Providers
Inference Providers
Model Providers
Image Generation
Audio/Speech Providers
Gateway/Proxy Providers
Local/Self-hosted
Regional/Specialized
Embedding Specialists
Memory/Agent Providers
Enterprise/Cloud
Quick Start
1
Simple Usage
2
With Configuration
Provider Support Matrix
tools, outputSchema, and stream work on every supported provider:
On OpenAI,
outputSchema uses response_format: json_schema; on other providers it routes through the AI SDK backend’s generateObject({ schema }). Both paths return a JSON string that matches the schema.
Agent with Different Models
tools and outputSchema work end-to-end on every supported provider (openai/..., anthropic/..., google/..., groq/..., mistral/..., ollama/..., and more). Tools are formatted once and translated per-provider by the AI SDK backend — the same contract litellm gives the Python SDK. Non-OpenAI providers stream pre-tool text as tokens when stream: true; see Streaming for tool-loop streaming behaviour. Fixed in PraisonAI PR #4412.Tools & Structured Output on any provider
Multi-Agent with Mixed Providers
Use different models for different Agent roles:Agent Model Selection by Task
Agent with Streaming
Environment-Based Model Selection
Model String Formats
PraisonAI resolves the vendor from your model string — a bareclaude-* or gemini-* name routes to Anthropic or Google without a prefix.
See Model Routing for the full routing rules, the complete decision table, and the
baseURL exception.Prefix Inference vs Aliases
Two different mechanisms decide where a model string goes. Prefix inference — the parser reads a bare name and infers the provider:
Convenience aliases — short names used only inside the provider-registry lookup:
Per-agent API key and baseURL
Pass credentials per agent — as of PraisonAI PR #4483 the constructor-timeapiKey is honoured across providers, not only for OpenAI. Env vars remain a fallback.
OpenAI-Compatible Providers
Use any OpenAI-compatible API:Local Providers (Ollama, LM Studio)
Agent with Custom Provider Config
For advanced use cases:Custom Provider Extension
Register your own provider:ProviderConfig Options
Custom transport and browser support are configurable onProviderConfig.
See Browser & Webview Runtimes for when to use each option.
Environment Variables
Related
Providers CLI
CLI commands
Provider Registry
Custom providers

