Zoo Code
The community continuation of Roo Code, set up through its OpenAI Compatible provider.
Point Zoo Code 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.Open the settings panel and choose OpenAI Compatible
Click the gear icon in the Zoo Code panel. OpenAI Compatible is the API Provider to pick; the named vendors in that list are not the route here.
Settings > ProvidersAPI Provider OpenAI Compatible Base URL https://api.tium.ai/v1 API Key sk-tium-... Model glm-5.3-flash Model Configuration Context Window 1000000 Max Output Tokens 327682.Fill in the Base URL, API Key and Model
There is no config file to paste, so the fields above are the instruction. Any slug from the catalog goes in the Model field.
3.Set the Model Configuration values before you start
Context Window and Max Output Tokens sit under Model Configuration and do not default to what we serve. Both are worth setting by hand rather than left at whatever the provider template assumes.
Check that it worked
Ask it something small in Code mode and watch the response arrive. Every response carries its cost and your remaining balance in the X-Tium-* headers.
Every response also carries its own cost and your remaining balance in the X-Tium-* headers. See the header reference.
What Zoo Code gets wrong
Tool-specific behaviour that surprises people, and what to do about it.
Zoo Code uses native tool calling only
Their documentation is explicit that there is no prompt-based fallback, so a model that cannot emit OpenAI-style tool_calls will not work in the agent modes at all. Pick a catalog model whose tool calling we certify; this is the one capability to confirm before you build a workflow on it.
The Base URL keeps its /v1
Their docs say only that the field is not OpenAI's own endpoint. The version segment belongs to the base URL here, the same as everywhere else on this site, and dropping it is the same 404 that catches people in Jan and Continue.
Coming from Roo Code, your settings carry over
Zoo Code keeps Roo Code's settings structure, so an existing OpenAI Compatible profile transfers with the same three fields. Check the Base URL survived the move rather than assuming it did.
There is no Fetch Models button
Zoo Code does not read the catalog for you on this provider, so the Model field is typed rather than picked. We serve an authenticated GET /v1/models if you want to see the current slugs first.