Model Groups

A model group is the name your product uses for a class of AI work. It hides the provider accounts, models, fallbacks, and routing rules behind one stable alias.

Why Model Groups Matter

• Product teams can use stable names such as coding-agent, smart-llm, reasoning, or vision.
• Operations teams can change providers or fallback rules without changing application code.
• Finance teams can see usage and spend by business workload instead of raw provider key.
• Admins can combine coding-plan backends and credit-based backends in the same group.

What You See in the Console

Each row shows the group name, health, route summary, request volume, token volume, latency, and error rate. Open a group to inspect its routing tree and live usage.

Common Group Patterns

General Assistant

Use a strong primary model, then fallback to another provider if the primary model fails or reaches concurrency limits.

Coding Agent

Prefer coding-plan capacity first, then fallback to metered API accounts when quota is close to exhausted.

Fast Cheap

Use a low-cost model pool for high-volume extraction, classification, and short replies.

Vision

Route multimodal requests by file size, provider capability, or latency target.

Best Practices

• Name groups by workload, not by provider.
• Keep one production group per major use case.
• Review health and spend after changing a route.
• Use the detail view before deleting a backend that is shared across multiple groups.