← ClaudeAtlas

extreme-router-gateway-enginelisted

AI Gateway routing, provider management, and core engine expertise for ExtremeRouter. Use when working on request routing, provider fallback, token refresh, format translation, streaming, or when the user asks about "how does routing work", "add a new provider", "fix the fallback logic", "optimize token usage", or mentions providers, models, or API compatibility.
rsalmn/ExtremeRouter · ★ 13 · AI & Automation · score 73
Install: claude install-skill rsalmn/ExtremeRouter
# AI Gateway Engine Expertise You are an expert in AI Gateway architecture, provider routing, and API compatibility. ## Core Concepts ### Request Flow ``` Client Request → /v1/* endpoint → Route handler (src/app/api/v1/*) → Chat handler (src/sse/handlers/chat.js) → Core orchestrator (open-sse/handlers/chatCore.js) → Provider executor (open-sse/executors/*) → Upstream provider API → Response translation (open-sse/translator/*) → Client response (SSE stream or JSON) ``` ### Key Components #### 1. Route Handlers (src/app/api/v1/*) - Receive client requests - Validate API keys - Delegate to chat handler - Handle errors #### 2. Chat Handler (src/sse/handlers/chat.js) - Parse request body - Resolve model/combo - Select provider account - Call core orchestrator - Handle combo/fusion routing #### 3. Core Orchestrator (open-sse/handlers/chatCore.js) - Detect source format (OpenAI/Claude/Gemini/etc) - Translate request to target format - Select executor - Execute request with retry/refresh - Translate response back to client format - Stream response to client - Track usage #### 4. Provider Executors (open-sse/executors/*) - Build provider-specific headers - Construct provider-specific URLs - Handle provider-specific auth (OAuth, API key, device code) - Parse provider-specific responses - Handle provider-specific errors #### 5. Format Translators (open-sse/translator/*) - Convert between API formats - Request translators: `openai-to-*`, `claude-to-*`, etc - Respon