---
title: "Assistant"
description: "The built-in Docus assistant is already configured in the app and can be enabled when the worker gets an AI gateway key."
canonical_url: "https://nimiq.dev/ai/assistant"
---
# Assistant

> The built-in Docus assistant is already configured in the app and can be enabled when the worker gets an AI gateway key.

The Developer Center already includes the Docus assistant module, but the backend is not live on the public worker yet. The UI is configured in the app, and the assistant becomes active once the deployment provides `AI_GATEWAY_API_KEY`.

<note>

The assistant is planned for a future rollout. The current site configuration already enables the floating input UI and the "Explain with AI" action, but the server route stays disabled until the AI gateway key is present.

</note>

## Current Configuration

The app config currently enables:

<table>
<thead>
  <tr>
    <th align="left">
      Feature
    </th>
    
    <th align="left">
      Status
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td align="left">
      Floating input
    </td>
    
    <td align="left">
      Enabled in app config
    </td>
  </tr>
  
  <tr>
    <td align="left">
      "Explain with AI" button
    </td>
    
    <td align="left">
      Enabled in app config
    </td>
  </tr>
  
  <tr>
    <td align="left">
      Assistant API route
    </td>
    
    <td align="left">
      Disabled until <code>
        AI_GATEWAY_API_KEY
      </code>
      
       is set
    </td>
  </tr>
</tbody>
</table>

## Runtime Details

When enabled, the assistant uses these Docus defaults:

<table>
<thead>
  <tr>
    <th align="left">
      Setting
    </th>
    
    <th align="left">
      Value
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td align="left">
      API route
    </td>
    
    <td align="left">
      <code>
        /__docus__/assistant
      </code>
    </td>
  </tr>
  
  <tr>
    <td align="left">
      MCP server
    </td>
    
    <td align="left">
      <code>
        /mcp
      </code>
    </td>
  </tr>
  
  <tr>
    <td align="left">
      Default model
    </td>
    
    <td align="left">
      <code>
        google/gemini-3-flash
      </code>
    </td>
  </tr>
</tbody>
</table>

That means the assistant will use the same built-in MCP server documented in [/ai/mcp](https://nimiq.dev/ai/mcp).

## What The Assistant Supports

Docus exposes configuration for:

<table>
<thead>
  <tr>
    <th align="left">
      Option
    </th>
    
    <th align="left">
      Purpose
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td align="left">
      <code>
        floatingInput
      </code>
    </td>
    
    <td align="left">
      Shows the floating prompt input on documentation pages
    </td>
  </tr>
  
  <tr>
    <td align="left">
      <code>
        explainWithAi
      </code>
    </td>
    
    <td align="left">
      Shows the "Explain with AI" action in the docs sidebar
    </td>
  </tr>
  
  <tr>
    <td align="left">
      <code>
        faqQuestions
      </code>
    </td>
    
    <td align="left">
      Seeds suggested questions for users
    </td>
  </tr>
  
  <tr>
    <td align="left">
      <code>
        shortcuts.focusInput
      </code>
    </td>
    
    <td align="left">
      Controls the keyboard shortcut for focusing the assistant
    </td>
  </tr>
  
  <tr>
    <td align="left">
      <code>
        icons.trigger
      </code>
    </td>
    
    <td align="left">
      Changes the trigger icon
    </td>
  </tr>
  
  <tr>
    <td align="left">
      <code>
        icons.explain
      </code>
    </td>
    
    <td align="left">
      Changes the explain-action icon
    </td>
  </tr>
</tbody>
</table>

## Rollout Path

To make the assistant live on the worker, the deployment needs an AI gateway key. Once that key is present, Docus mounts the assistant API route automatically and the configured UI starts using it.


## Sitemap

See the full [sitemap](https://nimiq.dev/sitemap.md) for all pages.