Provider registry & routing (chat/tools/vision + circuit breaker)
Generated from
mcp/patterns.registry.json— do not edit by hand; change the registry and runbun run patterns:build.
Index card — the docs below are the canonical explanation; deep-tier pattern pages additionally carry invariants and emulation notes.
Category: AI · Tier: light · Risk: medium — external LLM providers with quota limits
Resolver functions pick an active chat, tool-calling, or vision LLM provider per turn and trip a Redis-backed circuit breaker on rate-limited providers.
When to use: Use when an app must route between multiple LLM providers by capability and needs cross-instance cooldown on failures.
Docs
Code
Machine-readable record: ai-provider-routing in mcp/patterns.registry.json.