Skip to content
Goose logo (Block)

Goose via Tokonomix

Point Goose's OpenAI provider host at Tokonomix — Block's autonomous agent on 130+ models and consensus, one key.

OpenAI provider (OPENAI_HOST)MCP extensionsAutonomous CLI + desktop agentApache-2.0 · open sourcemacOS · Linux · Windows
Goose — Block's autonomous agent, via Tokonomix

What is Goose?

Goose (by Block) is an open-source autonomous agent that installs, runs and tests code on your machine — CLI and desktop. It uses the OpenAI provider for any OpenAI-compatible endpoint, and its capabilities extend through MCP.

  • Runs long autonomous sessions: plans, edits, runs commands and reacts to output.
  • Selects a provider via goose configure or environment variables.
  • For OpenAI-compatible endpoints, set OPENAI_HOST to the endpoint URL.
  • Extends through MCP servers, so a consensus tool fits right in.

Why route Goose through Tokonomix?

  • Goose runs long unattended chains with tool calls — drive it with a direct model like anthropic/claude-sonnet-4-6, and call consensus as an opt-in cross-check on planning-only steps.
  • One key, 130+ models — change the model without touching providers.
  • Per-call spend caps bound an autonomous run; cost is metered in your dashboard.
  • Region / origin routing for a code-executing agent.

Connect Tokonomix to Goose

Select the OpenAI provider and set OPENAI_HOST to the Tokonomix endpoint. Goose normalises a trailing /v1, so the path resolves correctly to chat completions.

# host + key via environment (NOT config.yaml)
export OPENAI_HOST=https://tokonomix.ai/api/v1
export OPENAI_API_KEY=tok_live_your-key

# ~/.config/goose/config.yaml (or via `goose configure`)
GOOSE_PROVIDER: openai
GOOSE_MODEL: anthropic/claude-sonnet-4-6
# Opt-in (planning/review only, no tool-calling): GOOSE_MODEL: tokonomix-consensus
Tool calling

Goose relies on tool calling, so pick a tool-capable model like anthropic/claude-sonnet-4-6. Consensus does not do tool calls — keep it as an opt-in review step only.

Verify it works

  • Run goose session and give it a small task.
  • Confirm it plans and executes using the Tokonomix model.
  • Check the call and token usage in your Tokonomix dashboard.

Model selection

Which model and endpoint should my agent use?

Pick by what your agent does, then swap the model id any time — every model in the catalog works through the same key.

What your agent doesUse this
Edits files / calls tools and streams responses (most coding agents)An Anthropic model via the Anthropic endpoint (tools + streaming both work)
Calls tools but does not need streaming (any model)The OpenAI-compatible endpoint with a single model id
Wants tools and streaming on a non-Anthropic modelRun non-streaming for now — streaming tool-calls on other providers is not enabled yet
Plain chat, no toolsEither endpoint; streaming is fine
Wants a cross-model verdict (consensus) on a high-stakes answerSet model to tokonomix-consensus on the OpenAI-compatible endpoint — note: consensus rejects tool requests (no tool-calling)
Endpoint & API reference (technical)

anthropic-messages → https://tokonomix.ai/api/anthropic — tools ✓, streaming ✓ (use an Anthropic model). openai-completions → https://tokonomix.ai/api/v1 — tools ✓ (single-model passthrough), streaming with tools not yet enabled. Plain chat: streaming works on both. Consensus: openai-completions, model tokonomix-consensus, no tools. Swap the model id to any slug returned by GET /api/v1/models.

Browse all models →

Related agents