Skip to main content
Your model stays exactly where it is — on the machine running Ollama, llama.cpp, vLLM, or LM Studio. To reach it from your phone, install a chat app that supports a custom OpenAI-compatible endpoint, and point it at https://api.tokios.com/v1 with your sk-tok-… API key. No VPN, no port forwarding, no exposing your home network. This page covers the OpenAI-compatible surface only. Few mobile chat apps expose a settable Anthropic base URL, so treat ANTHROPIC_BASE_URL as a desktop/CLI feature (see Use Claude Code) unless you find one that does.

​
The one gotcha that breaks every setup: /v1 or not

Mobile apps disagree on whether the base URL field wants the /v1 suffix:
  • Apps that want /v1 included: Maid, Open WebUI, LibreChat. Use https://api.tokios.com/v1.
  • Apps that want the bare host and append the path themselves: Chatbox. Use https://api.tokios.com (no /v1).
Get this backwards and requests 404 or never leave the app. Check the field’s placeholder text — if it shows a default ending in /v1 (for example https://api.openai.com/v1), include /v1. If the field is just labeled API Host, leave /v1 off.

​
Apps to avoid

  • Chatbox on iOS — do not use. A confirmed, unresolved bug (chatboxai/chatbox#3516) means custom OpenAI-compatible endpoints with Bearer-key auth fail on iOS: non-proxied requests go through a WKWebView fetch() that enforces CORS, and the Authorization header triggers a preflight OPTIONS request that Tokios (like most local-facing servers) doesn’t answer the way the app expects. Chatbox on Android does not have this bug — see below.
  • Reins and Enchanted — do not use. Both apps speak only the Ollama-native API (/api/chat, /api/generate). Tokios exposes the OpenAI-compatible (/v1/chat/completions) and Anthropic-compatible (/v1/messages) surfaces, not the raw Ollama API, so these apps cannot connect at all unless a future release adds an OpenAI-compatible mode.
All three apps below take a custom endpoint and a Bearer API key. None of them are Tokios-specific, so confirm the exact field labels in-app before you rely on them — they can change between app versions.

​
Pal Chat

Supports custom OpenAI-compatible endpoints and bring-your-own-key providers.

​
Apollo (by Liquid AI)

Connects to local or custom AI servers that use the OpenAI-compatible format, and lets you specify a model identifier for custom backends.

​
3sparks Chat

Describes itself as compatible with OpenAI-compatible APIs, local and online. Exact field labels are unconfirmed.
Do not use Chatbox on iOS for this — see Apps to avoid above.

​
Power option: run a hosted web UI and install it as a PWA

If you want a fuller chat interface (chat history, multiple deployments, system prompts) instead of a dedicated native app, host Open WebUI or LibreChat on a server, point its OpenAI-compatible connection at Tokios, and install it on your phone as a Progressive Web App:
1

Configure Tokios on the server

In Open WebUI: Admin → Settings → Connections → OpenAI API. Set:LibreChat’s equivalent is its OpenAI-compatible custom endpoint configuration on the server side.
2

Install the PWA on your phone

Open the hosted instance’s URL in your phone’s browser, then:
  • iOS (Safari only): tap Share → Add to Home Screen.
  • Android (Chrome, Firefox, Brave, Edge): open the browser menu → Install app / Add to Home Screen.
The Tokios configuration lives entirely on the server — your phone never holds the API key directly; it just opens the installed PWA against your hosted Open WebUI or LibreChat instance.

​
Next steps

Quickstart

Go from zero to a working connector, deployment, and API key.

Add API keys to local models

Scope a key to specific deployments before you hand it to a mobile app.