Provider choice · per task
Your model. Your route.
Connect your own API credentials for OpenAI, OpenRouter, Kimi (Moonshot), DeepSeek, Anthropic, Google Gemini or xAI Grok. Desk AI includes no provider keys or usage credits.
Separate settings for each task
Choose independent providers and models for replies and general assistant, image and receipt understanding, text polish, call summaries, dictation transcription and call transcription. The provider catalog helps you choose, and custom model IDs are supported. Compatibility depends on the provider, account and model: image understanding requires image input. OpenAI, OpenRouter and Gemini speech transcription adapters are available; the other providers do not currently support speech transcription in Desk AI. Image generation and text-to-speech (TTS) are not included.
Credentials and data
Provider keys are kept in your local Chrome profile and sent from the trusted extension worker only to the selected provider when you run a task. Keys are not sent to the WhatsApp page, panel state, product site or licensing service. Local Chrome storage is not independently encrypted; anyone with access to your browser profile or extension developer tools may be able to retrieve a key.
Requests may include relevant business excerpts, visible chat text and images for drafts; only selected text for polish; transcript and names for summaries; and audio for transcription after you start that action. Each provider's own privacy, retention and billing terms apply. API access is billed by the provider to your account.
ChatGPT plan use
OpenAI API billing is separate from a ChatGPT subscription. Desk AI does not currently implement Sign in with ChatGPT or ChatGPT-plan inference. OpenAI's documented open-source flow requires a local HTTP callback listener, secure OAuth validation and protected token storage. A Chrome extension cannot bind the documented 127.0.0.1 listener by itself; any future sign-in needs a trusted native companion or another officially supported host. We do not promise a ready-to-use subscription sign-in button. See the official open-source guide ↗ and models and inference requirements ↗.
For the implementation inventory and verification requirements, see the provider guide and release plan.