| 0:00–0:20 | AI Hub in Gluesync 2.3 | How AI Hub fits the Core Hub control plane: AI Studio, Query Studio AI, Query Forge, Core Hub MCP, and the Enterprise brain. Your models, not your data in another AI silo. |
| 0:20–1:05 | Bring your own models | Register providers under Settings → LLM providers: OpenAI, Anthropic, Azure OpenAI, OpenAI-compatible endpoints, local Ollama. Credentials stay encrypted in Core Hub; model traffic does not proxy through MOLO17. Model catalog and routing preview by capability, residency, health, price, and cost, without spending tokens. |
| 1:05–1:50 | AI Studio agents | Chat with governed agents under the caller’s Core Hub permissions. Build and publish immutable agent versions with instructions, versioned skills, routing policy, limits, and output contracts. Durable runs with idempotency, cancellation, and event history. |
| 1:50–2:00 | Break | |
| 2:00–2:50 | SQL AI: Query Studio AI, Query Forge, gluesync.ai | Query Studio AI drafts and completes SQL from the schema it already knows; you review before you run. PII-tagged columns are masked before anything reaches the model. Federated queries across agents with Query Forge (jdbc:gluesync://, Personal API Tokens). The gluesync.ai virtual table: answer, proposed SQL, citations, conversation ID in one row. Proposed SQL is never auto-executed. |
| 2:50–3:30 | Core Hub MCP for AI clients | Connect Claude, ChatGPT, Cursor, or any MCP client to Core Hub over Streamable HTTP (/mcp/http) or SSE (/mcp) with a session token or Personal API Token. The 125 built-in tools run under the caller’s RBAC. Read-only mode and tool allow-lists. |
| 3:30–3:50 | Govern access and spend | Scoped platform keys (gsa_), agent and model allow-lists, rate limits, expiry, budgets, usage, and audit records. Native run API and OpenAI-compatible endpoint for your applications. |
| 3:50–4:00 | Wrap-up | Your rollout checklist, open questions, next steps. |