Back to models
RetiredChat Models

Groq

Compound

Historical multi-tool Groq system retired September 21, 2026, with no direct replacement listed in its shutdown notice.

Historical systemMigration guide
Open AppBrowse All Models

At a glance

Know the model before you prompt.

Historical API specifications
Context window
Not verified
Maximum output
Not verified
Inputs → output
Text → Text
Knowledge cutoff
Not verified

API model ID: groq/compound

Capabilities & boundaries

What it supports. Where the limits are.

Tool support requires the appropriate API integration; a supported tool is not automatically active in every chat.

Historical API features and tools

  • Previously orchestrated multiple built-in tool steps to complete a single user request
  • Combined underlying model routing with a hosted tool workflow rather than acting as one standalone model
  • Historical integrations included web search, website visits, code execution and Wolfram Alpha
  • Designed for tasks needing more than the single tool call offered by Compound Mini

Before you choose

  • The system has shut down. Historical examples and overview pages do not make groq/compound an active API model.
  • No verified system-wide context, maximum output or knowledge cutoff is stated here; routed-model specifications are not automatically the compound system's limits.
  • The documented system did not expose arbitrary user-defined custom tools. A replacement must provide its own supported tools and orchestration.
  • More tool steps add failure modes and potentially cost. Validate citations, execution results and permissions rather than trusting a final summary alone.

Reasoning behavior

Historical Compound behavior concerned orchestration across models and tools, not a documented single reasoning-effort control. In a replacement, separate reasoning depth, tool selection, step limits and termination criteria so each can be tested.

  • Remove the retired ID from active routing and fallback configuration after reviewing the application's migration requirements.
  • Define a maximum tool budget, timeout, retry policy and human-approval boundary for the replacement. Model function calling alone does not provide those controls.
  • Browser automation had already been removed before the system shutdown. Do not treat a historic browser_automation configuration as a working capability.

Put it to work

Start with a more useful prompt.

Original migration and workflow examples from EZ Ai Assist. Use these with an available model and the appropriate tools; the retired system cannot run new requests.

Workflow 01

Map a multi-tool migration

Separate the model's job from the surrounding orchestration.

From the old agent workflow and logs below, map each step to its purpose, required tool, inputs, outputs and failure path. Propose a replacement using currently available components that I identify. Include permissions, timeouts, retry limits and a final validation step. Do not assume a retired system has a drop-in replacement or that any tool is already connected.

Workflow 02

Plan a source-backed investigation

Turn a broad research request into bounded, checkable steps.

Create a research plan for the question below with a maximum of five tool steps. Specify the evidence needed, an appropriate source type, a stop condition and how conflicting results should be handled. If tools are available, request approval before execution; otherwise return only the plan. Do not present planned searches as completed research.

Workflow 03

Evaluate an agent's execution trace

Audit the intermediate work rather than only the final answer.

Audit this supplied agent trace and final answer. For every consequential claim, identify the tool result or source that supports it. Flag unauthorized actions, repeated calls, unhandled errors and unsupported conclusions. Recommend the smallest orchestration changes that would prevent recurrence, with a regression case for each. Do not invent missing trace entries.

Developer reference

Groq API pricing

These are Groq API reference prices, not EZ Ai Assist subscription prices.

View EZ Ai Assist plans

Compound is retired, so this guide does not advertise current prices for requests that can no longer run.

  • A replacement's cost depends on the chosen models, number of tool steps and service terms. Estimate and measure those components separately.
  • The retirement notice lists no direct replacement or transferable pricing promise. Historical system rates should not be treated as a current offer.

Common questions

A few things worth knowing.

What is Compound's current status?

Groq decommissioned Compound on September 21, 2026. Its model ID no longer accepts supported requests. The changelog and deprecation notice take precedence over older descriptions of an available system.

Was it just another language model?

No. Compound combined underlying models with built-in tool orchestration. Replacing it can require changes to tool execution, retries, permissions and result validation, not just changing a model string.

Did Compound Mini survive the shutdown?

No. Both groq/compound and groq/compound-mini were decommissioned on the same date. Switching to Mini is not a supported way to recover the old service.

Which model replaces it directly?

Groq lists no direct replacement. Select a current model and supported tools based on your workflow, then test the complete integration. This guide does not invent a replacement endorsement.

Should I retain the old API configuration?

Keep historical configuration for audit or migration reference where appropriate, but do not rely on the retired ID for active traffic or fallback. Review scheduled tasks and retry loops that might keep sending failing requests.

Why does this guide include migration prompts?

They help an available model analyze requirements, plan safe research and audit execution traces. They are original workflow aids, not runnable examples for the retired endpoint.

Does this notice prove the model is unavailable in every app?

It establishes Groq's API lifecycle, not the internal routing of every application. Check EZ Ai Assist for current workspace access and do not infer app behavior from a catalog entry alone.

Check the source

Official documentation

Specifications and API prices checked on . Example prompts and workflow advice are editorial guidance from EZ Ai Assist.

Same provider

More from Groq

Groq

GPT-OSS 120B

OpenAI's larger open-weight reasoning model on Groq, with tool use, structured outputs, and a 131K context window.

Groq

GPT-OSS 20B

Compact open-weight reasoning on Groq for focused text tasks, with structured outputs, tool use, and automatic caching.

Groq

Compound Mini

Historical single-tool Groq system retired September 21, 2026. Explore its former workflow and migration considerations.

Groq

LLaMA 3.3 70B Versatile

Meta's 70B text model on Groq with 131K context. Free/developer access ended; committed-spend enterprise contracts are exempt.