durar-ai 2026.4.4

package/docs/providers/bedrock.md

@@ -0,0 +1,273 @@
+---
+summary: "Use Amazon Bedrock (Converse API) models with Durar"
+read_when:
+  - You want to use Amazon Bedrock models with Durar
+  - You need AWS credential/region setup for model calls
+title: "Amazon Bedrock"
+---
+
+# Amazon Bedrock
+
+Durar can use **Amazon Bedrock** models via pi‑ai’s **Bedrock Converse**
+streaming provider. Bedrock auth uses the **AWS SDK default credential chain**,
+not an API key.
+
+## What pi-ai supports
+
+- Provider: `amazon-bedrock`
+- API: `bedrock-converse-stream`
+- Auth: AWS credentials (env vars, shared config, or instance role)
+- Region: `AWS_REGION` or `AWS_DEFAULT_REGION` (default: `us-east-1`)
+
+## Automatic model discovery
+
+Durar can automatically discover Bedrock models that support **streaming**
+and **text output**. Discovery uses `bedrock:ListFoundationModels` and
+`bedrock:ListInferenceProfiles`, and results are cached (default: 1 hour).
+
+How the implicit provider is enabled:
+
+- If `plugins.entries.amazon-bedrock.config.discovery.enabled` is `true`,
+  Durar will try discovery even when no AWS env marker is present.
+- If `plugins.entries.amazon-bedrock.config.discovery.enabled` is unset,
+  Durar only auto-adds the
+  implicit Bedrock provider when it sees one of these AWS auth markers:
+  `AWS_BEARER_TOKEN_BEDROCK`, `AWS_ACCESS_KEY_ID` +
+  `AWS_SECRET_ACCESS_KEY`, or `AWS_PROFILE`.
+- The actual Bedrock runtime auth path still uses the AWS SDK default chain, so
+  shared config, SSO, and IMDS instance-role auth can work even when discovery
+  needed `enabled: true` to opt in.
+
+Config options live under `plugins.entries.amazon-bedrock.config.discovery`:
+
+```json5
+{
+  plugins: {
+    entries: {
+      "amazon-bedrock": {
+        config: {
+          discovery: {
+            enabled: true,
+            region: "us-east-1",
+            providerFilter: ["anthropic", "amazon"],
+            refreshInterval: 3600,
+            defaultContextWindow: 32000,
+            defaultMaxTokens: 4096,
+          },
+        },
+      },
+    },
+  },
+}
+```
+
+Notes:
+
+- `enabled` defaults to auto mode. In auto mode, Durar only enables the
+  implicit Bedrock provider when it sees a supported AWS env marker.
+- `region` defaults to `AWS_REGION` or `AWS_DEFAULT_REGION`, then `us-east-1`.
+- `providerFilter` matches Bedrock provider names (for example `anthropic`).
+- `refreshInterval` is seconds; set to `0` to disable caching.
+- `defaultContextWindow` (default: `32000`) and `defaultMaxTokens` (default: `4096`)
+  are used for discovered models (override if you know your model limits).
+- For explicit `models.providers["amazon-bedrock"]` entries, Durar can still
+  resolve Bedrock env-marker auth early from AWS env markers such as
+  `AWS_BEARER_TOKEN_BEDROCK` without forcing full runtime auth loading. The
+  actual model-call auth path still uses the AWS SDK default chain.
+
+## Onboarding
+
+1. Ensure AWS credentials are available on the **gateway host**:
+
+```bash
+export AWS_ACCESS_KEY_ID="AKIA..."
+export AWS_SECRET_ACCESS_KEY="..."
+export AWS_REGION="us-east-1"
+# Optional:
+export AWS_SESSION_TOKEN="..."
+export AWS_PROFILE="your-profile"
+# Optional (Bedrock API key/bearer token):
+export AWS_BEARER_TOKEN_BEDROCK="..."
+```
+
+2. Add a Bedrock provider and model to your config (no `apiKey` required):
+
+```json5
+{
+  models: {
+    providers: {
+      "amazon-bedrock": {
+        baseUrl: "https://bedrock-runtime.us-east-1.amazonaws.com",
+        api: "bedrock-converse-stream",
+        auth: "aws-sdk",
+        models: [
+          {
+            id: "us.anthropic.claude-opus-4-6-v1:0",
+            name: "Claude Opus 4.6 (Bedrock)",
+            reasoning: true,
+            input: ["text", "image"],
+            cost: { input: 0, output: 0, cacheRead: 0, cacheWrite: 0 },
+            contextWindow: 200000,
+            maxTokens: 8192,
+          },
+        ],
+      },
+    },
+  },
+  agents: {
+    defaults: {
+      model: { primary: "amazon-bedrock/us.anthropic.claude-opus-4-6-v1:0" },
+    },
+  },
+}
+```
+
+## EC2 Instance Roles
+
+When running Durar on an EC2 instance with an IAM role attached, the AWS SDK
+can use the instance metadata service (IMDS) for authentication. For Bedrock
+model discovery, Durar only auto-enables the implicit provider from AWS env
+markers unless you explicitly set
+`plugins.entries.amazon-bedrock.config.discovery.enabled: true`.
+
+Recommended setup for IMDS-backed hosts:
+
+- Set `plugins.entries.amazon-bedrock.config.discovery.enabled` to `true`.
+- Set `plugins.entries.amazon-bedrock.config.discovery.region` (or export `AWS_REGION`).
+- You do **not** need a fake API key.
+- You only need `AWS_PROFILE=default` if you specifically want an env marker
+  for auto mode or status surfaces.
+
+```bash
+# Recommended: explicit discovery enable + region
+Durar config set plugins.entries.amazon-bedrock.config.discovery.enabled true
+Durar config set plugins.entries.amazon-bedrock.config.discovery.region us-east-1
+
+# Optional: add an env marker if you want auto mode without explicit enable
+export AWS_PROFILE=default
+export AWS_REGION=us-east-1
+```
+
+**Required IAM permissions** for the EC2 instance role:
+
+- `bedrock:InvokeModel`
+- `bedrock:InvokeModelWithResponseStream`
+- `bedrock:ListFoundationModels` (for automatic discovery)
+- `bedrock:ListInferenceProfiles` (for inference profile discovery)
+
+Or attach the managed policy `AmazonBedrockFullAccess`.
+
+## Quick setup (AWS path)
+
+```bash
+# 1. Create IAM role and instance profile
+aws iam create-role --role-name EC2-Bedrock-Access \
+  --assume-role-policy-document '{
+    "Version": "2012-10-17",
+    "Statement": [{
+      "Effect": "Allow",
+      "Principal": {"Service": "ec2.amazonaws.com"},
+      "Action": "sts:AssumeRole"
+    }]
+  }'
+
+aws iam attach-role-policy --role-name EC2-Bedrock-Access \
+  --policy-arn arn:aws:iam::aws:policy/AmazonBedrockFullAccess
+
+aws iam create-instance-profile --instance-profile-name EC2-Bedrock-Access
+aws iam add-role-to-instance-profile \
+  --instance-profile-name EC2-Bedrock-Access \
+  --role-name EC2-Bedrock-Access
+
+# 2. Attach to your EC2 instance
+aws ec2 associate-iam-instance-profile \
+  --instance-id i-xxxxx \
+  --iam-instance-profile Name=EC2-Bedrock-Access
+
+# 3. On the EC2 instance, enable discovery explicitly
+Durar config set plugins.entries.amazon-bedrock.config.discovery.enabled true
+Durar config set plugins.entries.amazon-bedrock.config.discovery.region us-east-1
+
+# 4. Optional: add an env marker if you want auto mode without explicit enable
+echo 'export AWS_PROFILE=default' >> ~/.bashrc
+echo 'export AWS_REGION=us-east-1' >> ~/.bashrc
+source ~/.bashrc
+
+# 5. Verify models are discovered
+Durar models list
+```
+
+## Inference profiles
+
+Durar discovers **regional and global inference profiles** alongside
+foundation models. When a profile maps to a known foundation model, the
+profile inherits that model's capabilities (context window, max tokens,
+reasoning, vision) and the correct Bedrock request region is injected
+automatically. This means cross-region Claude profiles work without manual
+provider overrides.
+
+Inference profile IDs look like `us.anthropic.claude-opus-4-6-v1:0` (regional)
+or `anthropic.claude-opus-4-6-v1:0` (global). If the backing model is already
+in the discovery results, the profile inherits its full capability set;
+otherwise safe defaults apply.
+
+No extra configuration is needed. As long as discovery is enabled and the IAM
+principal has `bedrock:ListInferenceProfiles`, profiles appear alongside
+foundation models in `Durar models list`.
+
+## Notes
+
+- Bedrock requires **model access** enabled in your AWS account/region.
+- Automatic discovery needs the `bedrock:ListFoundationModels` and
+  `bedrock:ListInferenceProfiles` permissions.
+- If you rely on auto mode, set one of the supported AWS auth env markers on the
+  gateway host. If you prefer IMDS/shared-config auth without env markers, set
+  `plugins.entries.amazon-bedrock.config.discovery.enabled: true`.
+- Durar surfaces the credential source in this order: `AWS_BEARER_TOKEN_BEDROCK`,
+  then `AWS_ACCESS_KEY_ID` + `AWS_SECRET_ACCESS_KEY`, then `AWS_PROFILE`, then the
+  default AWS SDK chain.
+- Reasoning support depends on the model; check the Bedrock model card for
+  current capabilities.
+- If you prefer a managed key flow, you can also place an OpenAI‑compatible
+  proxy in front of Bedrock and configure it as an OpenAI provider instead.
+
+## Guardrails
+
+You can apply [Amazon Bedrock Guardrails](https://docs.aws.amazon.com/bedrock/latest/userguide/guardrails.html)
+to all Bedrock model invocations by adding a `guardrail` object to the
+`amazon-bedrock` plugin config. Guardrails let you enforce content filtering,
+topic denial, word filters, sensitive information filters, and contextual
+grounding checks.
+
+```json5
+{
+  plugins: {
+    entries: {
+      "amazon-bedrock": {
+        config: {
+          guardrail: {
+            guardrailIdentifier: "abc123", // guardrail ID or full ARN
+            guardrailVersion: "1", // version number or "DRAFT"
+            streamProcessingMode: "sync", // optional: "sync" or "async"
+            trace: "enabled", // optional: "enabled", "disabled", or "enabled_full"
+          },
+        },
+      },
+    },
+  },
+}
+```
+
+- `guardrailIdentifier` (required) accepts a guardrail ID (e.g. `abc123`) or a
+  full ARN (e.g. `arn:aws:bedrock:us-east-1:123456789012:guardrail/abc123`).
+- `guardrailVersion` (required) specifies which published version to use, or
+  `"DRAFT"` for the working draft.
+- `streamProcessingMode` (optional) controls whether guardrail evaluation runs
+  synchronously (`"sync"`) or asynchronously (`"async"`) during streaming. If
+  omitted, Bedrock uses its default behavior.
+- `trace` (optional) enables guardrail trace output in the API response. Set to
+  `"enabled"` or `"enabled_full"` for debugging; omit or set `"disabled"` for
+  production.
+
+The IAM principal used by the gateway must have the `bedrock:ApplyGuardrail`
+permission in addition to the standard invoke permissions.

package/docs/providers/chutes.md

@@ -0,0 +1,103 @@
+---
+title: "Chutes"
+summary: "Chutes setup (OAuth or API key, model discovery, aliases)"
+read_when:
+  - You want to use Chutes with Durar
+  - You need the OAuth or API key setup path
+  - You want the default model, aliases, or discovery behavior
+---
+
+# Chutes
+
+[Chutes](https://chutes.ai) exposes open-source model catalogs through an
+OpenAI-compatible API. Durar supports both browser OAuth and direct API-key
+auth for the bundled `chutes` provider.
+
+- Provider: `chutes`
+- API: OpenAI-compatible
+- Base URL: `https://llm.chutes.ai/v1`
+- Auth:
+  - OAuth via `Durar onboard --auth-choice chutes`
+  - API key via `Durar onboard --auth-choice chutes-api-key`
+  - Runtime env vars: `CHUTES_API_KEY`, `CHUTES_OAUTH_TOKEN`
+
+## Quick start
+
+### OAuth
+
+```bash
+Durar onboard --auth-choice chutes
+```
+
+Durar launches the browser flow locally, or shows a URL + redirect-paste
+flow on remote/headless hosts. OAuth tokens auto-refresh through Durar auth
+profiles.
+
+Optional OAuth overrides:
+
+- `CHUTES_CLIENT_ID`
+- `CHUTES_CLIENT_SECRET`
+- `CHUTES_OAUTH_REDIRECT_URI`
+- `CHUTES_OAUTH_SCOPES`
+
+### API key
+
+```bash
+Durar onboard --auth-choice chutes-api-key
+```
+
+Get your key at
+[chutes.ai/settings/api-keys](https://chutes.ai/settings/api-keys).
+
+Both auth paths register the bundled Chutes catalog and set the default model
+to `chutes/zai-org/GLM-4.7-TEE`.
+
+## Discovery behavior
+
+When Chutes auth is available, Durar queries the Chutes catalog with that
+credential and uses the discovered models. If discovery fails, Durar falls
+back to a bundled static catalog so onboarding and startup still work.
+
+## Default aliases
+
+Durar also registers three convenience aliases for the bundled Chutes
+catalog:
+
+- `chutes-fast` -> `chutes/zai-org/GLM-4.7-FP8`
+- `chutes-pro` -> `chutes/deepseek-ai/DeepSeek-V3.2-TEE`
+- `chutes-vision` -> `chutes/chutesai/Mistral-Small-3.2-24B-Instruct-2506`
+
+## Built-in starter catalog
+
+The bundled fallback catalog includes current Chutes refs such as:
+
+- `chutes/zai-org/GLM-4.7-TEE`
+- `chutes/zai-org/GLM-5-TEE`
+- `chutes/deepseek-ai/DeepSeek-V3.2-TEE`
+- `chutes/deepseek-ai/DeepSeek-R1-0528-TEE`
+- `chutes/moonshotai/Kimi-K2.5-TEE`
+- `chutes/chutesai/Mistral-Small-3.2-24B-Instruct-2506`
+- `chutes/Qwen/Qwen3-Coder-Next-TEE`
+- `chutes/openai/gpt-oss-120b-TEE`
+
+## Config example
+
+```json5
+{
+  agents: {
+    defaults: {
+      model: { primary: "chutes/zai-org/GLM-4.7-TEE" },
+      models: {
+        "chutes/zai-org/GLM-4.7-TEE": { alias: "Chutes GLM 4.7" },
+        "chutes/deepseek-ai/DeepSeek-V3.2-TEE": { alias: "Chutes DeepSeek V3.2" },
+      },
+    },
+  },
+}
+```
+
+## Notes
+
+- OAuth help and redirect-app requirements: [Chutes OAuth docs](https://chutes.ai/docs/sign-in-with-chutes/overview)
+- API-key and OAuth discovery both use the same `chutes` provider id.
+- Chutes models are registered as `chutes/<model-id>`.

package/docs/providers/claude-max-api-proxy.md

@@ -0,0 +1,163 @@
+---
+summary: "Community proxy to expose Claude subscription credentials as an OpenAI-compatible endpoint"
+read_when:
+  - You want to use Claude Max subscription with OpenAI-compatible tools
+  - You want a local API server that wraps Claude Code CLI
+  - You want to evaluate subscription-based vs API-key-based Anthropic access
+title: "Claude Max API Proxy"
+---
+
+# Claude Max API Proxy
+
+**claude-max-api-proxy** is a community tool that exposes your Claude Max/Pro subscription as an OpenAI-compatible API endpoint. This allows you to use your subscription with any tool that supports the OpenAI API format.
+
+<Warning>
+This path is technical compatibility only. Anthropic has blocked some subscription
+usage outside Claude Code in the past. You must decide for yourself whether to use
+it and verify Anthropic's current terms before relying on it.
+</Warning>
+
+## Why Use This?
+
+| Approach                | Cost                                                | Best For                                   |
+| ----------------------- | --------------------------------------------------- | ------------------------------------------ |
+| Anthropic API           | Pay per token (~$15/M input, $75/M output for Opus) | Production apps, high volume               |
+| Claude Max subscription | $200/month flat                                     | Personal use, development, unlimited usage |
+
+If you have a Claude Max subscription and want to use it with OpenAI-compatible tools, this proxy may reduce cost for some workflows. API keys remain the clearer policy path for production use.
+
+## How It Works
+
+```
+Your App → claude-max-api-proxy → Claude Code CLI → Anthropic (via subscription)
+     (OpenAI format)              (converts format)      (uses your login)
+```
+
+The proxy:
+
+1. Accepts OpenAI-format requests at `http://localhost:3456/v1/chat/completions`
+2. Converts them to Claude Code CLI commands
+3. Returns responses in OpenAI format (streaming supported)
+
+## Installation
+
+```bash
+# Requires Node.js 20+ and Claude Code CLI
+npm install -g claude-max-api-proxy
+
+# Verify Claude CLI is authenticated
+claude --version
+```
+
+## Usage
+
+### Start the server
+
+```bash
+claude-max-api
+# Server runs at http://localhost:3456
+```
+
+### Test it
+
+```bash
+# Health check
+curl http://localhost:3456/health
+
+# List models
+curl http://localhost:3456/v1/models
+
+# Chat completion
+curl http://localhost:3456/v1/chat/completions \
+  -H "Content-Type: application/json" \
+  -d '{
+    "model": "claude-opus-4",
+    "messages": [{"role": "user", "content": "Hello!"}]
+  }'
+```
+
+### With Durar
+
+You can point Durar at the proxy as a custom OpenAI-compatible endpoint:
+
+```json5
+{
+  env: {
+    OPENAI_API_KEY: "not-needed",
+    OPENAI_BASE_URL: "http://localhost:3456/v1",
+  },
+  agents: {
+    defaults: {
+      model: { primary: "openai/claude-opus-4" },
+    },
+  },
+}
+```
+
+This path uses the same proxy-style OpenAI-compatible route as other custom
+`/v1` backends:
+
+- native OpenAI-only request shaping does not apply
+- no `service_tier`, no Responses `store`, no prompt-cache hints, and no
+  OpenAI reasoning-compat payload shaping
+- hidden Durar attribution headers (`originator`, `version`, `User-Agent`)
+  are not injected on the proxy URL
+
+## Available Models
+
+| Model ID          | Maps To         |
+| ----------------- | --------------- |
+| `claude-opus-4`   | Claude Opus 4   |
+| `claude-sonnet-4` | Claude Sonnet 4 |
+| `claude-haiku-4`  | Claude Haiku 4  |
+
+## Auto-Start on macOS
+
+Create a LaunchAgent to run the proxy automatically:
+
+```bash
+cat > ~/Library/LaunchAgents/com.claude-max-api.plist << 'EOF'
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
+<plist version="1.0">
+<dict>
+  <key>Label</key>
+  <string>com.claude-max-api</string>
+  <key>RunAtLoad</key>
+  <true/>
+  <key>KeepAlive</key>
+  <true/>
+  <key>ProgramArguments</key>
+  <array>
+    <string>/usr/local/bin/node</string>
+    <string>/usr/local/lib/node_modules/claude-max-api-proxy/dist/server/standalone.js</string>
+  </array>
+  <key>EnvironmentVariables</key>
+  <dict>
+    <key>PATH</key>
+    <string>/usr/local/bin:/opt/homebrew/bin:~/.local/bin:/usr/bin:/bin</string>
+  </dict>
+</dict>
+</plist>
+EOF
+
+launchctl bootstrap gui/$(id -u) ~/Library/LaunchAgents/com.claude-max-api.plist
+```
+
+## Links
+
+- **npm:** [https://www.npmjs.com/package/claude-max-api-proxy](https://www.npmjs.com/package/claude-max-api-proxy)
+- **GitHub:** [https://github.com/atalovesyou/claude-max-api-proxy](https://github.com/atalovesyou/claude-max-api-proxy)
+- **Issues:** [https://github.com/atalovesyou/claude-max-api-proxy/issues](https://github.com/atalovesyou/claude-max-api-proxy/issues)
+
+## Notes
+
+- This is a **community tool**, not officially supported by Anthropic or Durar
+- Requires an active Claude Max/Pro subscription with Claude Code CLI authenticated
+- The proxy runs locally and does not send data to any third-party servers
+- Streaming responses are fully supported
+
+## See Also
+
+- [Anthropic provider](/providers/anthropic) - Native Durar integration with Claude CLI or API keys
+- [OpenAI provider](/providers/openai) - For OpenAI/Codex subscriptions

package/docs/providers/cloudflare-ai-gateway.md

@@ -0,0 +1,71 @@
+---
+title: "Cloudflare AI Gateway"
+summary: "Cloudflare AI Gateway setup (auth + model selection)"
+read_when:
+  - You want to use Cloudflare AI Gateway with Durar
+  - You need the account ID, gateway ID, or API key env var
+---
+
+# Cloudflare AI Gateway
+
+Cloudflare AI Gateway sits in front of provider APIs and lets you add analytics, caching, and controls. For Anthropic, Durar uses the Anthropic Messages API through your Gateway endpoint.
+
+- Provider: `cloudflare-ai-gateway`
+- Base URL: `https://gateway.ai.cloudflare.com/v1/<account_id>/<gateway_id>/anthropic`
+- Default model: `cloudflare-ai-gateway/claude-sonnet-4-5`
+- API key: `CLOUDFLARE_AI_GATEWAY_API_KEY` (your provider API key for requests through the Gateway)
+
+For Anthropic models, use your Anthropic API key.
+
+## Quick start
+
+1. Set the provider API key and Gateway details:
+
+```bash
+Durar onboard --auth-choice cloudflare-ai-gateway-api-key
+```
+
+2. Set a default model:
+
+```json5
+{
+  agents: {
+    defaults: {
+      model: { primary: "cloudflare-ai-gateway/claude-sonnet-4-5" },
+    },
+  },
+}
+```
+
+## Non-interactive example
+
+```bash
+Durar onboard --non-interactive \
+  --mode local \
+  --auth-choice cloudflare-ai-gateway-api-key \
+  --cloudflare-ai-gateway-account-id "your-account-id" \
+  --cloudflare-ai-gateway-gateway-id "your-gateway-id" \
+  --cloudflare-ai-gateway-api-key "$CLOUDFLARE_AI_GATEWAY_API_KEY"
+```
+
+## Authenticated gateways
+
+If you enabled Gateway authentication in Cloudflare, add the `cf-aig-authorization` header (this is in addition to your provider API key).
+
+```json5
+{
+  models: {
+    providers: {
+      "cloudflare-ai-gateway": {
+        headers: {
+          "cf-aig-authorization": "Bearer <cloudflare-ai-gateway-token>",
+        },
+      },
+    },
+  },
+}
+```
+
+## Environment note
+
+If the Gateway runs as a daemon (launchd/systemd), make sure `CLOUDFLARE_AI_GATEWAY_API_KEY` is available to that process (for example, in `~/.Durar/.env` or via `env.shellEnv`).

package/docs/providers/deepgram.md

@@ -0,0 +1,93 @@
+---
+summary: "Deepgram transcription for inbound voice notes"
+read_when:
+  - You want Deepgram speech-to-text for audio attachments
+  - You need a quick Deepgram config example
+title: "Deepgram"
+---
+
+# Deepgram (Audio Transcription)
+
+Deepgram is a speech-to-text API. In Durar it is used for **inbound audio/voice note
+transcription** via `tools.media.audio`.
+
+When enabled, Durar uploads the audio file to Deepgram and injects the transcript
+into the reply pipeline (`{{Transcript}}` + `[Audio]` block). This is **not streaming**;
+it uses the pre-recorded transcription endpoint.
+
+Website: [https://deepgram.com](https://deepgram.com)  
+Docs: [https://developers.deepgram.com](https://developers.deepgram.com)
+
+## Quick start
+
+1. Set your API key:
+
+```
+DEEPGRAM_API_KEY=dg_...
+```
+
+2. Enable the provider:
+
+```json5
+{
+  tools: {
+    media: {
+      audio: {
+        enabled: true,
+        models: [{ provider: "deepgram", model: "nova-3" }],
+      },
+    },
+  },
+}
+```
+
+## Options
+
+- `model`: Deepgram model id (default: `nova-3`)
+- `language`: language hint (optional)
+- `tools.media.audio.providerOptions.deepgram.detect_language`: enable language detection (optional)
+- `tools.media.audio.providerOptions.deepgram.punctuate`: enable punctuation (optional)
+- `tools.media.audio.providerOptions.deepgram.smart_format`: enable smart formatting (optional)
+
+Example with language:
+
+```json5
+{
+  tools: {
+    media: {
+      audio: {
+        enabled: true,
+        models: [{ provider: "deepgram", model: "nova-3", language: "en" }],
+      },
+    },
+  },
+}
+```
+
+Example with Deepgram options:
+
+```json5
+{
+  tools: {
+    media: {
+      audio: {
+        enabled: true,
+        providerOptions: {
+          deepgram: {
+            detect_language: true,
+            punctuate: true,
+            smart_format: true,
+          },
+        },
+        models: [{ provider: "deepgram", model: "nova-3" }],
+      },
+    },
+  },
+}
+```
+
+## Notes
+
+- Authentication follows the standard provider auth order; `DEEPGRAM_API_KEY` is the simplest path.
+- Override endpoints or headers with `tools.media.audio.baseUrl` and `tools.media.audio.headers` when using a proxy.
+- Output follows the same audio rules as other providers (size caps, timeouts, transcript injection).