Tool support requires the appropriate API integration; a supported tool is not automatically active in every chat.
Historical API features and tools
Previously selected at most one built-in tool call per request for a focused task
Historically combined model routing with integrated tools instead of exposing only a standalone model
Documented built-in web search, website visits, code execution and Wolfram Alpha capabilities when available
A historical single-tool alternative to the larger Compound system's multi-step tool orchestration
Before you choose
Retired: the groq/compound-mini API ID cannot be used for new requests. Historical documentation is not evidence of present availability.
The reviewed sources do not verify a current system-wide context, output limit or cutoff. Do not borrow those limits from an underlying routed model.
The system did not provide arbitrary user-defined custom tools. A replacement may require an application-managed tool loop and permission checks.
The built-in browser_automation tool had already retired on June 12, 2026. Historical tool lists should not be treated as current capabilities.
Reasoning behavior
Compound Mini was a tool-orchestration system, not a single model with a verified universal reasoning-effort setting. For a replacement, configure the chosen model and tool policy independently; do not assume GPT-OSS settings transfer to the retired system ID.
Inventory saved prompts, background jobs and fallback routes that still name groq/compound-mini. Stop routing new work to the retired ID.
A replacement must reproduce the needed tool behavior, not just return a similar text answer. Test failures, citations and tool authorization explicitly.
The example prompts below are migration aids for an available model. They do not restore the retired system or automatically provide search and execution tools.
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
Audit a retired single-tool integration
Find where the old system is still assumed to work.
Review the integration snippets and logs I provide for a retired single-tool AI system. Identify references to its model ID, scheduled jobs, retries and fallback behavior. For each dependency, state the required replacement capability and a verification test. Do not claim a replacement is drop-in compatible or execute any migration changes.
Workflow 02
Specify a one-step research task
Make the desired behavior portable to an available tool-enabled model.
Using an available search tool if one is configured, answer the single factual question below with a source URL and retrieval date. Keep the task to one focused lookup. If no search tool is available, say so and ask for source material rather than inventing a current answer. Separate the source's claim from your interpretation.
Workflow 03
Create a safe calculation handoff
Describe a tool contract and check its result.
Turn this calculation request into a tool contract: inputs, units, validation rules, expected output and error cases. Use an available calculation tool only if it is configured, then check the result against a simple independent estimate. If you cannot execute it, provide the specification and mark the result as not run.
Developer reference
Groq API pricing
These are Groq API reference prices, not EZ Ai Assist subscription prices.
Compound Mini is retired. There is no current executable service tariff to quote for this ID; historical prices are not presented as an available offer.
Price a replacement using its actual model, tool calls and hosting terms. Do not reuse an old blended system estimate.
Groq's shutdown table gives no direct replacement. Tool implementation and validation may be additional work rather than a simple model-ID substitution.
Common questions
A few things worth knowing.
Is Compound Mini still available on Groq?
No. Groq's changelog confirms decommissioning on September 21, 2026. Requests to groq/compound-mini are no longer supported, even if older overview text describes its former capabilities.
Why keep this page?
It preserves the existing reference URL and explains what an older integration used to do. The page is clearly historical and offers migration checks rather than promoting the retired API as a current option.
How did Mini differ from Compound?
Mini was designed around a single tool call for a focused task; Compound supported multi-step orchestration. That distinction matters when specifying the behavior a replacement should preserve.
Is there a recommended drop-in replacement?
Groq's shutdown notice lists none. Choose an available model and implement the necessary tool behavior, permissions and tests. Do not assume a model that generates tool calls recreates the complete former system.
Can the old browser automation tool still run?
No. Groq's Compound changelog says browser_automation retired June 12, 2026, before both systems were shut down. A new browser workflow needs a separately supported integration.
Why are token limits and prices missing?
The reviewed sources do not establish current system-wide limits or an executable tariff for this retired ID. Guessing from an underlying model would make the historical system look more certain and available than it is.
Where should I use these example prompts?
Use them with an available model for planning and testing a migration. Search or calculation steps still require configured tools. A prompt does not reactivate Compound Mini.
Check the source
Official documentation
Specifications and API prices checked on . Example prompts and workflow advice are editorial guidance from EZ Ai Assist.