Goose

Create your API key →

Mint an aireserve_api_… key in the portal — every Goose session is then metered and billed through your organization.

Goose configures providers in ~/.config/goose/config.yaml (provider reference). For Claude models, use the anthropic provider pointed at the gateway’s host root:

GOOSE_PROVIDER: anthropic
GOOSE_MODEL: claude-sonnet-4-6
ANTHROPIC_HOST: https://api.aireserve.com   # host root — goose appends /v1/messages
keyring: false

export ANTHROPIC_API_KEY="$AIRESERVE_API_KEY"   # your aireserve_api_… key
goose run -t "your prompt"                      # or `goose` for the interactive session

For GPT models (or any gateway model over the OpenAI dialect), swap the provider block:

GOOSE_PROVIDER: openai
GOOSE_MODEL: gpt-5.4-mini
OPENAI_HOST: https://api.aireserve.com   # host root — NO /v1
keyring: false

export OPENAI_API_KEY="$AIRESERVE_API_KEY"
goose run -t "your prompt"

Goose hosts are roots, not /v1 URLs. Unlike most OpenAI-flavored tools, goose builds the path itself: OPENAI_HOST gets v1/chat/completions appended (via its OPENAI_BASE_PATH default) and ANTHROPIC_HOST gets /v1/messages. If you see a 404, the usual cause is a /v1 already on the host doubling the path. Keys never go in config.yaml — goose ignores them there; use the environment variable (or goose’s keyring/secrets.yaml).

Verify

Run the one-shot command above. Goose answers in the terminal, and the request appears on your usage page — metered against your key, tool calls included.

⌘I

Getting started

Connect your tool

Models

Capabilities

Migrate

Data & privacy

Create your API key →

Verify

Create your API key →

​Verify

Verify