Connect

Goose

Block's open-source agent, which splits the endpoint across two variables.

Setup

Point Goose at Tium

You need the base URL https://api.tium.ai/v1 and an API key from your dashboard. Keys are shown once at creation.

  1. 1.Set the three variables

    Goose reaches an OpenAI-compatible endpoint through its built-in OpenAI provider, configured by environment rather than by a provider block.

    # Note the split: OPENAI_HOST carries no version segment,
# because OPENAI_BASE_PATH supplies it.
export OPENAI_HOST=https://api.tium.ai
export OPENAI_BASE_PATH=v1/chat/completions
export OPENAI_API_KEY=$TIUM_API_KEY

  2. 2.Run goose configure and choose the OpenAI provider

    The wizard asks for the host and the key. If it does not offer a base path, the environment variable above is what supplies it.

Worth knowing

What Goose gets wrong

Tool-specific behaviour that surprises people, and what to do about it.

OPENAI_HOST must not include /v1

This is the one that catches people, and Goose's own troubleshooting says a 404 usually means the base path is wrong. Everywhere else on this site the base URL owns the version segment; Goose is the exception, because it joins the host to OPENAI_BASE_PATH itself. Give it the bare origin and let the base path carry v1.

Elsewhere

Other tools

The same base URL and key work anywhere that takes an OpenAI-compatible endpoint.