Cavaridge Academy

What Cavaridge AI is, how it routes through the gateway, and where Ducky fits in.

--- title: Meet Cavaridge AI status: draft note: AI-generated first-pass transcript pending video production + SME review. --- Welcome to Cavaridge™ Academy. In this six-minute lesson, we'll cover what Cavaridge AI actually is, how it routes through the platform, and where Ducky fits into your team's daily flow. ## The shape Cavaridge AI is the umbrella for every AI-powered surface across the platform: Studio for chat and content, document analysis, research, report generation, and the in-product agents inside AEGIS, Cavaridge Operations, and the rest of the suite. You'll see Ducky everywhere. Ducky is the user-facing AI personality — a Cavalier King Charles Spaniel with a blue hard hat. Ducky is the brand of the experience. Behind Ducky is the **Cavaridge AI gateway**: an internal routing layer with one master OpenRouter key and per-app service tokens. You will never see the gateway as a user, and your apps will never call OpenRouter directly. They call the gateway. ## Why one gateway Three things land on a single gateway: - **Single point of LLM cost control.** Per-tenant spend caps live in `tenantConfig` and are enforced at the gateway. Apps don't get to decide how much they spend on your behalf. - **Provider failover.** If a model class degrades, the gateway routes to a comparable alternative inside the same task class — without the app having to know. - **Single audit point.** Every prompt and completion is recorded in Langfuse with tenant id, model, latency, token count, and cost. When someone asks "why is our LLM bill high?" you have one place to look. ## What this means for your team Three rules to internalize: 1. **You don't manage API keys.** Don't ask for an OpenRouter key, a Claude key, or any other model-provider credential. The platform handles this. If a feature needs more capacity, it's a `tenantConfig` change, not a key rotation. 2. **You don't pick models.** The gateway picks. If a feature defaults to a heavier model, that's an architectural decision in the agent — not a user setting. Trust the routing; report regressions through Pulse if quality drops. 3. **Ducky is the brand.** Spaniel, the gateway, and the model layer are internal. Customer-facing copy says Cavaridge AI. Customer-facing imagery and tone is Ducky. ## What's next In the next module we'll work hands-on in Studio: chat with citations, how to verify them, and what to do when output looks plausible but isn't grounded.

Meet Cavaridge AI

Knowledge check