> ## Documentation Index
> Fetch the complete documentation index at: https://docs.moxus.cloud/llms.txt
> Use this file to discover all available pages before exploring further.

# Browser extensions

> Configure Sider, ChatGPT Sidebar, and other browser extensions with custom API support.

Browser extensions are often used for webpage summaries, translation, rewriting, and sidebar chat. If the extension supports OpenAI-compatible APIs, it can connect to Moxus AI.

## Common values

| Field    | Value                                             |
| -------- | ------------------------------------------------- |
| Provider | OpenAI / Custom API / OpenAI Compatible           |
| Base URL | `https://moxus.cloud/v1`                          |
| API Key  | `sk-your-key`                                     |
| Model    | Copy the exact model name from Models and pricing |

## Sider

<Steps>
  <Step title="Open Sider settings">
    Click the Sider icon on the right side of the browser and open Sider settings.
  </Step>

  <Step title="Find model or API provider settings">
    Open General settings, choose custom API key in the AI access area, then click Settings for OpenAI.

    <img src="https://mintcdn.com/moxus-cloud/DgOc9Y6ZmJ9TiNBD/images/sider-provider-settings.png?fit=max&auto=format&n=DgOc9Y6ZmJ9TiNBD&q=85&s=168b4efc7c857e93e37d41057063fa09" alt="Sider general settings and OpenAI settings entry" width="1351" height="891" data-path="images/sider-provider-settings.png" />
  </Step>

  <Step title="Choose a custom OpenAI-compatible endpoint">
    In the OpenAI configuration window, use a custom API key and proxy URL.
  </Step>

  <Step title="Set the Base URL">
    Set the API proxy URL to `https://moxus.cloud/v1`.
  </Step>

  <Step title="Set the API key">
    Set API key to `sk-your-key`, then check or save the configuration.

    <img src="https://mintcdn.com/moxus-cloud/DgOc9Y6ZmJ9TiNBD/images/sider-openai-config.png?fit=max&auto=format&n=DgOc9Y6ZmJ9TiNBD&q=85&s=7972152a56246851fa20e7894cd81ba3" alt="Sider OpenAI API key and proxy URL settings" width="977" height="713" data-path="images/sider-openai-config.png" />
  </Step>

  <Step title="Choose a model and test">
    Save the settings, choose an available model, and send a test message to confirm Sider returns a response.

    <img src="https://mintcdn.com/moxus-cloud/DgOc9Y6ZmJ9TiNBD/images/sider-chat-test.png?fit=max&auto=format&n=DgOc9Y6ZmJ9TiNBD&q=85&s=96ecb45a80f61ff045f61178de460eb6" alt="Sider chat test result" width="1033" height="929" data-path="images/sider-chat-test.png" />
  </Step>
</Steps>

## ChatGPT Sidebar

1. Open extension settings.
2. Choose custom API or OpenAI API.
3. Set endpoint to `https://moxus.cloud/v1`.
4. Enter your API key.
5. If the extension asks for a model, enter the exact model name from Models and pricing.

## Other browser assistants

Most extensions use different field names for the same values:

| Extension field               | Value                                             |
| ----------------------------- | ------------------------------------------------- |
| API Host / API URL / Base URL | `https://moxus.cloud/v1` or `https://moxus.cloud` |
| API Key / Token               | `sk-your-key`                                     |
| Model / Model ID              | Exact model name from Models and pricing          |

<Warning>
  Browser extensions store keys in local extension settings. Do not use a main account key on public computers or untrusted extensions. Create a separate low-quota key instead.
</Warning>

## Troubleshooting

<AccordionGroup>
  <Accordion title="Should I include Bearer in the key field?">
    Usually no. Most extensions only need the `sk-` key and add `Bearer` automatically. Only enter the full Authorization header if the extension explicitly asks for it.
  </Accordion>

  <Accordion title="Webpage summary fails but chat works">
    The extension may be sending too much context or unsupported page content. Select a smaller page range or choose a longer-context model.
  </Accordion>

  <Accordion title="I am worried about key leakage">
    Create a separate API key for browser extensions and set a low quota limit. Delete the key when you no longer use the extension.
  </Accordion>
</AccordionGroup>

## Next steps

* [Billing](/en/platform/billing)
* [Usage](/en/platform/dashboard-and-usage)