multi-router.aidocs

Agents & Editors

Claude for Office

Connecting the Claude add-ins for Excel, PowerPoint, Word and Outlook to a Claude Proxy as a gateway.

Claude for Office is Anthropic's add-in for Microsoft 365 apps. Its sign-in screen can connect to a gateway instead of a Claude account, sending Anthropic Messages requests to a Claude Proxy. The add-in runs in the browser from https://pivot.claude.ai, and a Claude Proxy answers those cross-origin requests.

Creating the router

  1. In Routers, create a Claude Proxy on the Anthropic route, or a Custom route with a model group of Anthropic models, with the Organization credential source. See Claude Proxy.
  2. Copy its id, such as rt_XXXXXXXX, from the router's page.
  3. In API Keys, create a key with the inference and models:read scopes. The add-in reads the model list with models:read.

Settings

The router header can be set only by a Microsoft 365 admin, in the add-in's deployment manifest; the sign-in screen has no field for headers. The admin sets these manifest values:

Manifest keyValue
gateway_urlhttps://api.multi-router.ai
gateway_api_formatanthropic
inference_headers{"X-MR-Router": "rt_XXXXXXXX"}
gateway_tokenThe person's Multi-Router API key, or left for the person to enter at sign-in

People then open the add-in, choose Cloud provider or gateway on the sign-in screen, choose Gateway, and enter the gateway URL and their Multi-Router API key if the manifest does not supply them. The add-in sends a test request when it connects. Each person needs their own API key so that Traffic and budgets apply to them.

Models

The add-in names Claude models by their Anthropic model ids and fills its model list from the Claude Proxy, which lists the models its route serves and the router has switched on. A model group on the Custom route therefore controls which models people can pick.

Checking the setup

Open the add-in in Excel, PowerPoint or Word after signing in, and ask Claude to say hello.

The request then appears in Traffic with the Claude Proxy in the Router column and the model, tokens and cost in the request detail. A reply with the requested model or router was not found means the router id is wrong, or the API key is not allowed to use that router. See Traffic and Troubleshooting.

Claude DesktopOpen WebUI
Was this helpful?