Skip to content
ITS INCOM AI

Integrations

Integrations

What any OpenAI-compatible tool needs to work with ITS INCOM AI: the base URL, a key and a model id. Which model to pick, the context window to set, and what the API does not do.

Last updated: 2026-11-03

A tool that speaks OpenAI's chat completions API works with ITS INCOM AI. It needs three values:

Setting Value
Base URL https://api.ai.itsincom.org/v1
API key a key from the dashboard, starting with sk-its-
Model a model id from the catalogue, written as it is there: qwen3.8-27b, not Qwen3.8 27B

Tools give the base URL different names: Base URL, API Base, api_url, baseURL, OPENAI_API_BASE. The value is the same everywhere, and it ends in /v1, without /chat/completions.

Where a tool asks for a provider type, choose OpenAI Compatible. Where it offers only OpenAI, choose it and change the base URL.

Tested, or from the documentation

Every page says which of the two it is.

  • Tested: we ran the example on the live API on the date given, with the version of the tool named on the page, and the page shows what came back.
  • From the documentation: the settings come from the tool's own documentation, read on the date given. We did not run the tool. If a setting does not work as written, tell us at segreteria@itsincom.it.
Tool What it is Status
Cline coding agent for VS Code from the documentation
Continue coding assistant for VS Code and JetBrains from the documentation
Roo Code coding agent for VS Code from the documentation
Kilo Code coding agent for VS Code and the terminal from the documentation
OpenCode coding agent for the terminal from the documentation
Aider coding assistant for the terminal tested
Zed code editor with an agent from the documentation
Open WebUI chat interface you host yourself from the documentation
n8n workflow automation from the documentation
LangChain Python framework tested
LlamaIndex Python framework tested
LiteLLM Python SDK and proxy SDK tested, proxy from the documentation
Vercel AI SDK TypeScript framework tested
OpenAI Agents SDK Python framework for agents tested

Which model

The catalogue lists the models ITS INCOM AI serves today, with their prices and the country where each one runs. This table adds what a tool needs to be told, as we served it on 3 November 2026.

Model Context window Tools Images Reasoning Pick it for
qwen3.8-27b 131,072 yes no before every answer; reasoning_effort: "none" switches it off coding agents, long files, long conversations
qwen3-coder-next 262,144 yes no no changes across a whole project
devstral-small-2-24b 131,072 yes yes no coding agents that work across many files
qwen3-coder-30b 262,144 yes no no quick code edits, questions about code
qwen3.6-35b 262,144 yes yes no chat, summaries, translation, extraction at a low price
gpt-oss-120b 131,072 yes no low, medium or high; it cannot be switched off problems that need reasoning, with short inputs
gemma-4-26b 262,144 yes yes no photos of documents, scans, structured data
gemma-4-31b 262,144 yes yes no photos of documents and scans, with a dense model
ministral-3-14b 262,144 yes yes no short answers, classification, the background tasks of chat apps
apertus-70b-instruct 16,384 no no no text in many languages, Swiss German and Romansh among them

Tools: we sent each model a request with a tool, with the OpenAI SDK, and it returned the call in OpenAI's shape. A coding agent needs a model with tools.

Context window. Set it in the tool to the number in this table. A tool that does not know it assumes its own default, and may send a conversation longer than the model can read.

Maximum output. Set it to 32,768 tokens or less. The API refuses a larger max_tokens with 422.

Reasoning

The models with an entry in the Reasoning column reason before they answer. The reasoning is not returned: tools that show a model's thinking show nothing for them. It is counted in usage.completion_tokens, billed as output, and it counts against max_tokens. With a low cap the answer comes back cut or empty, with finish_reason: "length".

On qwen3.8-27b, "reasoning_effort": "none" switches reasoning off for a request. Asked for one sentence about the Gotthard tunnel on 11 October 2026, it used 176 output tokens with reasoning and 47 without. Each tool page shows how to send the field, where the tool allows it. More in Every parameter.

What the API does not do

  • Anthropic's Messages API. /v1/messages answers 404 with unknown_endpoint. Tools that speak only Anthropic's format, such as Claude Code, cannot connect directly.
  • Fill-in-the-middle. /v1/completions passes the prompt to the model as written, but refuses suffix. Tab completion built on fill-in-the-middle does not work here: Continue's autocomplete, Zed's edit predictions. Chat, edits and agents do.
  • Streaming on the Responses API. /v1/responses answers 501 to stream: true. Tools that stream and can use either API have to use chat completions; the pages of n8n and the OpenAI Agents SDK show the setting.
  • Parameters it does not know. A field that is not in Every parameter gets a 400 that names it. Some tools send fields of other engines when you fill in their settings, such as top_k, min_p or prompt_cache_key. Leave those settings empty. repetition_penalty is accepted.
  • Embeddings from other models. /v1/embeddings always answers with bge-m3: 1,024 dimensions, at most 32 texts per request. See Embeddings.

/v1/models lists every model ITS INCOM AI serves, and some of them do not chat: bge-m3, bge-reranker-v2-m3, whisper-1, whisper-1-hd, tts-1, and the picture and video models. When a tool fills its model menu from that list, choose a chat model.

Headers

Where a tool lets you add HTTP headers, X-Siati-Tier sets the tier of its requests. The zone where a request ran comes back in the X-Zona header of the answer.

Search the docs

Type to search…