@burtson-labs/bandit-engine 2.0.39 → 2.0.41

package/dist/modals/chat-modal/chat-modal.mjs

@@ -3,11 +3,11 @@ import {
   MAX_WINDOWED_HEIGHT,
   MIN_WINDOWED_HEIGHT,
   chat_modal_default
-} from "../../chunk-ECRNIAG6.mjs";
-import "../../chunk-QYH2T4L5.mjs";
-import "../../chunk-CDQYBO3Q.mjs";
+} from "../../chunk-3E57HLDV.mjs";
+import "../../chunk-LYWVYBKU.mjs";
+import "../../chunk-CX3INLYJ.mjs";
 import "../../chunk-XUBYA5I7.mjs";
-import "../../chunk-QU5S5QQP.mjs";
+import "../../chunk-54ZQ3FSN.mjs";
 import "../../chunk-KCI46M23.mjs";
 import "../../chunk-BJTO5JO5.mjs";
 export {

package/dist/public-types.d.mts

@@ -1,4 +1,4 @@
-export { t as AIChatRequest, u as AIChatResponse, w as AIGenerateRequest, x as AIGenerateResponse, y as AIMessage, s as AIModel, A as AIProviderConfig, g as ChatConfig, h as ChatModalProps, g as ChatProviderProps, b as FeatureEvaluation, F as FeatureFlagConfig, a as FeatureKey, f as FeatureMatrix, m as GatewayChatRequest, n as GatewayChatResponse, j as GatewayContract, o as GatewayGenerateRequest, p as GatewayGenerateResponse, G as GatewayHealthResponse, r as GatewayMemoryRecord, d as GatewayMemoryResponse, l as GatewayMessage, k as GatewayMessageContent, c as GatewayModel, q as GatewayModelsResponse, P as PackageSettings, S as SubscriptionTier, T as TrialUsage, i as VoiceModelsResponse } from './gateway-B0LJ3-jT.mjs';
+export { t as AIChatRequest, u as AIChatResponse, w as AIGenerateRequest, x as AIGenerateResponse, y as AIMessage, s as AIModel, A as AIProviderConfig, g as ChatConfig, h as ChatModalProps, g as ChatProviderProps, b as FeatureEvaluation, F as FeatureFlagConfig, a as FeatureKey, f as FeatureMatrix, m as GatewayChatRequest, n as GatewayChatResponse, j as GatewayContract, o as GatewayGenerateRequest, p as GatewayGenerateResponse, G as GatewayHealthResponse, r as GatewayMemoryRecord, d as GatewayMemoryResponse, l as GatewayMessage, k as GatewayMessageContent, c as GatewayModel, q as GatewayModelsResponse, P as PackageSettings, S as SubscriptionTier, T as TrialUsage, i as VoiceModelsResponse } from './gateway-5yt_3QDP.mjs';
 import 'react';
 
 interface StoredBrandingConfig {

package/dist/public-types.d.ts

@@ -1,4 +1,4 @@
-export { t as AIChatRequest, u as AIChatResponse, w as AIGenerateRequest, x as AIGenerateResponse, y as AIMessage, s as AIModel, A as AIProviderConfig, g as ChatConfig, h as ChatModalProps, g as ChatProviderProps, b as FeatureEvaluation, F as FeatureFlagConfig, a as FeatureKey, f as FeatureMatrix, m as GatewayChatRequest, n as GatewayChatResponse, j as GatewayContract, o as GatewayGenerateRequest, p as GatewayGenerateResponse, G as GatewayHealthResponse, r as GatewayMemoryRecord, d as GatewayMemoryResponse, l as GatewayMessage, k as GatewayMessageContent, c as GatewayModel, q as GatewayModelsResponse, P as PackageSettings, S as SubscriptionTier, T as TrialUsage, i as VoiceModelsResponse } from './gateway-B0LJ3-jT.js';
+export { t as AIChatRequest, u as AIChatResponse, w as AIGenerateRequest, x as AIGenerateResponse, y as AIMessage, s as AIModel, A as AIProviderConfig, g as ChatConfig, h as ChatModalProps, g as ChatProviderProps, b as FeatureEvaluation, F as FeatureFlagConfig, a as FeatureKey, f as FeatureMatrix, m as GatewayChatRequest, n as GatewayChatResponse, j as GatewayContract, o as GatewayGenerateRequest, p as GatewayGenerateResponse, G as GatewayHealthResponse, r as GatewayMemoryRecord, d as GatewayMemoryResponse, l as GatewayMessage, k as GatewayMessageContent, c as GatewayModel, q as GatewayModelsResponse, P as PackageSettings, S as SubscriptionTier, T as TrialUsage, i as VoiceModelsResponse } from './gateway-5yt_3QDP.js';
 import 'react';
 
 interface StoredBrandingConfig {

package/docs/01_quickstart.md

@@ -7,6 +7,7 @@ The quickstart gateway exposes the contract Bandit expects out of the box:
 - `GET /api/health` — confirm connectivity and list configured providers.
 - `GET /api/models` and `GET /api/models/:provider` — populate the model switcher and provider tabs.
 - `POST /api/chat/completions` and `POST /api/generate` — default OpenAI-style chat/generation when no provider override is supplied.
+- `POST /api/bandit/chat/completions` — Bandit AI chat completions (OpenAI-compatible).
 - `POST /api/openai|azure-openai|anthropic/chat/completions` — provider-scoped chat completions.
 - `POST /api/openai|azure-openai|anthropic/generate` — provider-scoped text generation.
 - `POST /api/ollama/chat` and `POST /api/ollama/generate` — native Ollama streaming routes.
@@ -23,16 +24,21 @@ The quickstart gateway exposes the contract Bandit expects out of the box:
    npm install
    npm run dev
    ```
-   The example server listens on `http://localhost:8080` and proxies to OpenAI, Azure OpenAI, Anthropic, or Ollama using provider-scoped endpoints. Providers without credentials respond with `501` until you wire them up.
+   The example server listens on `http://localhost:8080` and proxies to Bandit AI, OpenAI, Azure OpenAI, Anthropic, or Ollama using provider-scoped endpoints. Providers without credentials respond with `501` until you wire them up.
 3. **Wrap your app with `ChatProvider`**:
    ```tsx
    import { ChatProvider } from "@burtson-labs/bandit-engine";
 
    <ChatProvider
      packageSettings={{
-       gatewayApiUrl: "http://localhost:8080",
-       defaultModel: "gpt-4.1-mini",
-       brandingConfigUrl: "/config.json"
+       gatewayApiUrl: "http://localhost:8080/api",
+       defaultModel: "bandit-core-1",
+       brandingConfigUrl: "/config.json",
+       aiProvider: {
+         type: "gateway",
+         gatewayUrl: "http://localhost:8080/api",
+         provider: "bandit"
+       }
      }}
    >
      {/* your routes */}

package/docs/02_gateway_api.md

@@ -18,16 +18,18 @@ Every request must include `Authorization: Bearer <token>`. Tokens are injected
 | `/api/tts`, `/api/stt`, `/api/tts/available-models` | POST/GET | Optional voice endpoints for advanced deployments. |
 
 ### Provider-specific chat/generation routes
-When the UI specifies a provider (OpenAI, Azure OpenAI, Anthropic, Ollama), Bandit Engine switches to provider-scoped endpoints automatically. Implement these routes alongside the core ones above:
+When the UI specifies a provider (Bandit AI, OpenAI, Azure OpenAI, Anthropic, Ollama), Bandit Engine switches to provider-scoped endpoints automatically. Implement these routes alongside the core ones above:
 
 | Provider | Chat endpoint | Generation endpoint |
 | --- | --- | --- |
+| Bandit AI | `POST /api/bandit/chat/completions` | `POST /api/bandit/generate`* |
 | OpenAI | `POST /api/openai/chat/completions` | `POST /api/openai/generate` |
 | Azure OpenAI | `POST /api/azure-openai/chat/completions` | `POST /api/azure-openai/generate` |
 | Anthropic | `POST /api/anthropic/chat/completions` | `POST /api/anthropic/generate` |
 | Ollama | `POST /api/ollama/chat` | `POST /api/ollama/generate` |
 
-> ℹ️ Bandit still includes the `provider` field in the request body for convenience, but the URL itself determines which upstream integration should run. Ollama uses `/chat` (not `/chat/completions`) to match its native API.
+> ℹ️ Bandit still includes the `provider` field in the request body for convenience, but the URL itself determines which upstream integration should run. Ollama uses `/chat` (not `/chat/completions`) to match its native API.  
+> \* `POST /api/bandit/generate` is optional today but mirrors the shape of `/api/chat/completions` for parity with other providers.
 
 If you only support a single upstream provider you may implement the matching provider-specific endpoints and omit the others. The `/api/chat/completions` and `/api/generate` routes remain useful as a “default” path when the frontend has no explicit provider preference.
 
@@ -42,11 +44,25 @@ app.use(express.json());
 app.get("/api/health", (req, res) => {
   res.json({
     status: "healthy",
-    providers: ["openai", "ollama"],
+    providers: ["bandit", "openai", "ollama"],
     version: "1.0.0"
   });
 });
 
+app.post("/api/bandit/chat/completions", async (req, res) => {
+  const response = await fetch(`${process.env.GATEWAY_URL}/completions`, {
+    method: "POST",
+    headers: {
+      "Content-Type": "application/json",
+      Authorization: `Bearer ${process.env.BANDIT_API_KEY}`
+    },
+    body: JSON.stringify(req.body)
+  });
+
+  res.status(response.status);
+  response.body?.pipe(res);
+});
+
 app.post("/api/openai/chat/completions", async (req, res) => {
   const { model, messages, stream = true } = req.body;
 

package/docs/03_provider_integration.md

@@ -3,7 +3,7 @@
 Bandit Engine routes every model invocation through your gateway but preserves provider-specific capabilities such as multimodal prompts, Azure deployment parameters, and local Ollama streaming. This guide summarizes the nuances for each supported provider and how to combine them with Bandit's feature flag system.
 
 ## Endpoints / API Usage
-- `POST /api/{provider}/chat/completions` — automatically selected when `provider` is set to `openai`, `azure-openai`, or `anthropic`.
+- `POST /api/{provider}/chat/completions` — automatically selected when `provider` is set to `bandit`, `openai`, `azure-openai`, `anthropic`, or `xai`.
 - `POST /api/{provider}/generate` — optional non-chat endpoint for custom workloads.
 - `GET /api/models/{provider}` — provider-specific model listing exposed in the management UI.
 
@@ -12,17 +12,18 @@ Bandit Engine routes every model invocation through your gateway but preserves p
 import { GatewayProvider } from "@burtson-labs/bandit-engine";
 
 const provider = new GatewayProvider({
-  provider: "openai",
+  provider: "bandit",
   gatewayUrl: "https://gateway.example.com",
   tokenFactory: () => localStorage.getItem("authToken") ?? ""
 });
 
-provider.listModelsByProvider("openai").subscribe(models => {
-  console.log("OpenAI models", models.map(model => model.name));
+provider.listModelsByProvider("bandit").subscribe(models => {
+  console.log("Bandit models", models.map(model => model.name));
 });
 ```
 
 ### Provider Notes
+- **Bandit AI**: Accepts OpenAI-format requests and automatically normalizes aliases such as `bandit-core-1`. Supports both auth tokens (UI) and API keys (CLI/partner usage) through the gateway.
 - **OpenAI & Azure OpenAI**: Send images as `image_url` entries alongside text segments. Azure requires `deploymentName` and `apiVersion` within the gateway configuration.
 - **Anthropic**: Supports the same streaming pipeline with Claude models and structured responses.
 - **Ollama**: Keeps images on the final user message through the `images` array and exposes `/api/ollama/chat` plus `/api/ollama/generate` endpoints.

package/docs/api_reference/media/02_gateway_api.md

@@ -18,16 +18,18 @@ Every request must include `Authorization: Bearer <token>`. Tokens are injected
 | `/api/tts`, `/api/stt`, `/api/tts/available-models` | POST/GET | Optional voice endpoints for advanced deployments. |
 
 ### Provider-specific chat/generation routes
-When the UI specifies a provider (OpenAI, Azure OpenAI, Anthropic, Ollama), Bandit Engine switches to provider-scoped endpoints automatically. Implement these routes alongside the core ones above:
+When the UI specifies a provider (Bandit AI, OpenAI, Azure OpenAI, Anthropic, Ollama), Bandit Engine switches to provider-scoped endpoints automatically. Implement these routes alongside the core ones above:
 
 | Provider | Chat endpoint | Generation endpoint |
 | --- | --- | --- |
+| Bandit AI | `POST /api/bandit/chat/completions` | `POST /api/bandit/generate`* |
 | OpenAI | `POST /api/openai/chat/completions` | `POST /api/openai/generate` |
 | Azure OpenAI | `POST /api/azure-openai/chat/completions` | `POST /api/azure-openai/generate` |
 | Anthropic | `POST /api/anthropic/chat/completions` | `POST /api/anthropic/generate` |
 | Ollama | `POST /api/ollama/chat` | `POST /api/ollama/generate` |
 
-> ℹ️ Bandit still includes the `provider` field in the request body for convenience, but the URL itself determines which upstream integration should run. Ollama uses `/chat` (not `/chat/completions`) to match its native API.
+> ℹ️ Bandit still includes the `provider` field in the request body for convenience, but the URL itself determines which upstream integration should run. Ollama uses `/chat` (not `/chat/completions`) to match its native API.  
+> \* `POST /api/bandit/generate` is optional today but mirrors the shape of `/api/chat/completions` for parity with other providers.
 
 If you only support a single upstream provider you may implement the matching provider-specific endpoints and omit the others. The `/api/chat/completions` and `/api/generate` routes remain useful as a “default” path when the frontend has no explicit provider preference.
 
@@ -42,11 +44,25 @@ app.use(express.json());
 app.get("/api/health", (req, res) => {
   res.json({
     status: "healthy",
-    providers: ["openai", "ollama"],
+    providers: ["bandit", "openai", "ollama"],
     version: "1.0.0"
   });
 });
 
+app.post("/api/bandit/chat/completions", async (req, res) => {
+  const response = await fetch(`${process.env.GATEWAY_URL}/completions`, {
+    method: "POST",
+    headers: {
+      "Content-Type": "application/json",
+      Authorization: `Bearer ${process.env.BANDIT_API_KEY}`
+    },
+    body: JSON.stringify(req.body)
+  });
+
+  res.status(response.status);
+  response.body?.pipe(res);
+});
+
 app.post("/api/openai/chat/completions", async (req, res) => {
   const { model, messages, stream = true } = req.body;
 

package/docs/api_reference/media/README.md

@@ -1,6 +1,6 @@
 # Bandit Gateway Node Example
 
-This example demonstrates a minimal HTTP gateway that proxies chat and generation requests to OpenAI, Azure OpenAI, Anthropic, or Ollama via provider-specific endpoints. Use it to validate your Bandit Engine integration before wiring up your production infrastructure.
+This example demonstrates a minimal HTTP gateway that proxies chat and generation requests to Bandit AI, OpenAI, Azure OpenAI, Anthropic, or Ollama via provider-specific endpoints. Use it to validate your Bandit Engine integration before wiring up your production infrastructure.
 
 ## Getting Started
 ```bash
@@ -10,6 +10,7 @@ npm run dev
 
 The server listens on `http://localhost:8080`. Configure the following environment variables as needed:
 
+- `BANDIT_API_KEY` – Optional; required when proxying to the Bandit API-key endpoint.
 - `OPENAI_API_KEY` – Optional; required when proxying to OpenAI.
 - `OLLAMA_URL` – Optional; defaults to `http://localhost:11434`.
 - `AZURE_OPENAI_CHAT_URL` / `AZURE_OPENAI_RESPONSES_URL` – Optional; set to your Azure deployment REST URLs when using Azure OpenAI.
@@ -33,5 +34,6 @@ The server listens on `http://localhost:8080`. Configure the following environme
 | `POST /api/anthropic/generate` | Anthropic text generation proxy. |
 | `POST /api/ollama/chat` | Native Ollama chat streaming proxy. |
 | `POST /api/ollama/generate` | Native Ollama generate proxy. |
+| `POST /api/bandit/chat/completions` | Bandit AI chat completions proxy. |
 
 These map directly to the requirements described in [`docs/02_gateway_api.md`](../../docs/02_gateway_api.md). Providers without credentials or URLs return `501 Not Implemented` responses so you can enable them incrementally.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@burtson-labs/bandit-engine",
-  "version": "2.0.39",
+  "version": "2.0.41",
   "license": "BUSL-1.1",
   "main": "dist/index.js",
   "module": "dist/index.mjs",