Groq models in Big-AGI

Running Groq in Big-AGI

Add your Groq API key and reach its catalog at Groq's own rates. Big-AGI adds no markup and no intermediary: the billing relationship runs directly between you and Groq.

• Your key, your billing. Usage is billed by Groq directly to your account.
• Built for speed. Groq's LPU hardware serves open models at hundreds of tokens per second, so long generations and agentic loops finish before you'd expect them to start.
• The real creator, labeled. Groq hosts OpenAI's GPT-OSS, Alibaba's Qwen, and Moonshot's Kimi; Big-AGI prefixes every model with who actually built it, not just who's serving it.
• Compound, priced through. Groq's own Compound and Compound Mini agentic systems chain web search, code execution, and browser automation on top of those models, billed at the underlying model's rate.

Why not just the Groq playground?

The playground proves the speed; it doesn't give you a workspace. Big-AGI adds persistent chats, personas, and attachments on top of the raw API, then puts that speed to work in Beam: run a Groq-hosted model next to Claude, GPT, and Gemini, and it's usually the first one back, sometimes by a wide margin.

Parameters, the key, and the chats stay yours to control instead of locked into a single-prompt tool.

Your keys and your data

Turn on Direct Connection and the browser calls Groq directly, bypassing the Big-AGI server, when your key is client-side and Groq allows it. Your keys stay in your browser. Chats are stored locally first, and sync only if you turn it on. The AI Inspector shows the exact request, the token counts, and a cost estimate.

Groq in Beam

Put a Groq-hosted model into a Beam next to Claude, GPT, and Gemini, and let its speed set the pace. Fusions then combine, cross-check, and synthesize the parallel answers instead of just picking the best one. Parallel runs use more tokens than a single chat.