Skip to main content
This page covers the most common questions and issues when setting up and using Tokios.

​
Setup & connectivity

A 503 means the Tokios gateway can’t reach an active connector tunnel for the requested model. Check that:
  1. The connector process is still running and connected.
  2. The model name in your API request matches a deployment you registered in the console.
  3. The device was approved during pairing and shows as online in the console’s Connectors tab. (If you run the advanced multi-model config-file path, also confirm the ConnectorId and upstreams in tokios-connector.json match the connector shown in the console.)
No. The connector only dials outbound to Tokios over WebSockets (port 443). Your firewall needs no changes, and nothing on your machine listens for inbound connections.
Yes. Point the upstream’s BaseUrl at the other machine — for example, http://192.168.1.50:11434/v1. No opt-in setting is needed: the connector forwards only to hosts named in its own config file, never to a URL supplied by the gateway. To lock an upstream to its host, add the host to AllowedHosts; a later BaseUrl edit that points somewhere else then fails at startup. See Connector Config.

​
API compatibility

Three: OpenAI Chat Completions (/v1/chat/completions), Anthropic Messages (/v1/messages), and OpenAI Responses (/v1/responses), plus /v1/models and /v1/messages/count_tokens. The gateway translates Messages and Responses to Chat Completions for your model. Provider-specific features that depend on a vendor’s own backend (OpenAI Assistants, Files, fine-tuning) are not available.
Yes. Set "stream": true in your request body. Tokios returns server-sent events in the standard OpenAI/Anthropic streaming format on all surfaces.
Yes. For SDK clients, set the base URL to https://api.tokios.com/v1 (with the /v1 suffix). For Anthropic-style clients that use ANTHROPIC_BASE_URL, set it to https://api.tokios.com (no /v1 — the client appends the path). Check your client’s docs for which form it expects.

​
Local models

Not by default. Tokios routes each request through the tunnel to your local model and streams the response back. The metering behind your usage page records token counts, latency, status, and identifiers only, and response bodies are never stored.A workspace admin can turn on request logging in the dashboard’s Settings. Tokios then keeps the request body of each API call for 7 days, encrypted at rest, with attachments stripped and secret-looking text redacted, and shows it under Prompt when you open a request in the request log. Only your workspace’s users can read stored prompts: admins see all of them, members only those sent with their own keys, and someone you shared a key with only if you allowed it for that key. You can turn it off, or delete every stored prompt, at any time. See Request logging.
Any server that exposes an OpenAI-compatible Chat Completions API: Ollama, llama.cpp, vLLM, and LM Studio are the most common. Set the upstream BaseUrl (including /v1) in tokios-connector.json. See Backends.
Yes. A single connector can serve several models using Routes + Upstreams, and you register a deployment (public name) for each. You can also run one connector per model. See Model Routing.

​
Account & billing

Yes — the community plan is free with no credit card required, giving you full access to run and evaluate Tokios with your own hardware.
In the console, go to API Keys, find the key, and click Revoke. The key stops authenticating immediately.