multi-router.aidocs

Agents & Editors

Goose

Connecting the Goose command-line agent to an Adaptive Router through its OpenAI provider.

Goose is an open-source agent with a command-line version and a desktop app. The command-line version connects to Multi-Router through its OpenAI provider, pointed at the Multi-Router address with the router header. The desktop app cannot send custom headers, so it cannot name a router.

Creating the router

Goose connects through an Adaptive Router, which accepts OpenAI Chat Completions requests and serves each one with the model it names, using the organization's provider key for that model's provider. Goose holds only the Multi-Router API key. See Adaptive Router. To set it up:

  1. In Model Groups, create or choose a model group with the models Goose should use. See Model Group.
  2. In Routers, choose New router, then Adaptive Router. Name it, choose the model group, and switch on the models to serve.
  3. Choose the organization's provider key for each provider in the group, and create the router. Its id, such as rt_XXXXXXXX, is on the router's page.
  4. In API Keys, create a key with the inference scope. It can be limited to this router. See API Key.

Every request carries the router id in the X-MR-Router header and the API key as a Bearer token, both set in Goose's settings below.

Settings

Goose reads its OpenAI provider settings from environment variables. OPENAI_HOST is the address without a path, OPENAI_BASE_PATH is the Chat Completions path, and OPENAI_CUSTOM_HEADERS holds the router header as Name=value:

Shellbash
export GOOSE_PROVIDER=openai
export GOOSE_MODEL=anthropic/claude-sonnet-4.6
export OPENAI_API_KEY='<Multi-Router API key>'
export OPENAI_HOST=https://api.multi-router.ai
export OPENAI_BASE_PATH=v1/chat/completions
export OPENAI_CUSTOM_HEADERS='X-MR-Router=rt_XXXXXXXX'

Models

An Adaptive Router names models by their Multi-Router catalog id, provider/model, such as anthropic/claude-sonnet-4.6, openai/gpt-5 or google/gemini-2.5-flash. The model must be switched on in the router's model group; a request for any other model is refused with a message listing the models the router serves. The settings on this page list each model id explicitly.

Goose sends some models, such as OpenAI's GPT-5 family, with the OpenAI Responses format to /v1/responses whatever OPENAI_BASE_PATH says. An Adaptive Router does not serve that format, and those requests are refused with 404. Use a model Goose sends with Chat Completions, such as anthropic/claude-sonnet-4.6.

Checking the setup

A first requestbash
goose run --no-session --quiet -t 'Reply exactly ready.'

The request then appears in Traffic with the Adaptive Router 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.

AmpAider
Was this helpful?