Skip to main content
You don’t have to open the dashboard and wire an orchestrator by hand. From any MCP-connected IDE (Claude Code, Cursor, Warp, Windsurf), the agent can create and configure a Theo key for a specific use case in a single tool call — and the result shows up in your hitheo dashboard immediately, ready to review or extend.

​
The fast path: “just coding”

Ask the agent, in plain language:
The agent calls theo_setup_key with use_case="coding". Theo:
  1. Creates a new API key.
  2. Pins it to a single strong code engine as a deterministic passthrough — no intent classification, skills, or guardrail routing, so every request goes straight to the coding model with no surprises.
  3. Returns the raw key (shown once) and a dashboard link.
You copy the key into your IDE’s Theo/OpenAI-compatible endpoint setting and you’re done. No canvas, no nodes.

​
Use cases

Pass a model to override the default for any use case, e.g. use_case="raw", model="anthropic/claude-opus-4.8".

​
Route by load (or any per-mode split)

Want light requests on a fast engine and heavy ones on a reasoning engine? Describe it, and the agent passes a routing array — Theo’s classifier splits each request into a mode and the binding pins that mode’s engine. No graph to build.
The agent calls theo_setup_key with:
Modes: fast, think, code, research, roast, genui, data_extraction. Engine ids include arca-velox-5.1, arca-magnus-5.1, anthropic/claude-sonnet-4.6, anthropic/claude-opus-4.8, anthropic/claude-haiku-4.5, google/gemini-2.5-pro, openai/gpt-4.1.

​
Custom logic → a full graph

For arbitrary branching/guardrail logic the user describes in prose, the agent can pass a graph ({ enabled, nodes, edges }) — a full orchestrator graph, applied as-is. See the Canvas graph schema for node/edge shapes. graph takes precedence over routing and use_case.

​
Configure a key you already have

The agent calls theo_configure_key. Same presets, applied to the key you name.

​
It round-trips to the dashboard

Both tools return a link like:
Open it and the Orchestrator lands directly on that key, showing exactly what the agent set up. From there you can layer on routing rules, skills, guardrails, or brand — the visual builder and the agent edit the same underlying config.

​
Requirements

  • The MCP server must be authenticated with a key that has the billing scope (needed to create keys). See Install.
  • The created key ships with completions, skills, and tools scopes.

​
See also