AI Providers
Genie uses one visible Coding provider/model route. The former Logistics role, Use one model toggle, and user-set clarification budget are retired. Legacy Logistics preferences are written only as compatibility mirrors and do not select another runtime route.
Supported provider families
Section titled “Supported provider families”| Provider | Use |
|---|---|
| OpenAI | Hosted OpenAI models and Responses-compatible AGENT tools |
| Anthropic | Hosted Claude models and native tool use |
| Hosted Gemini models and function calling | |
| xAI / Grok | Hosted Grok models through xAI’s compatible API |
| Custom / Local | An OpenAI-compatible local model, gateway, or self-hosted endpoint |
The current model list is curated in the app. Retired saved selections are normalized to supported replacements before dispatch.
What to configure
Section titled “What to configure”- provider
- model
- reasoning effort, where supported
- provider API key or token
- one OpenAI-compatible endpoint when using Custom / Local
Run Test Connection before saving a custom endpoint.
One route, several workflows
Section titled “One route, several workflows”- AGENT uses the selected Coding route for its sealed understanding and tool loop.
- Retained script-authoring compatibility paths run Stage A then Stage B on the same route.
- LAYOUT preflight, style, and generation also use the same route.
- Internal clarification limits remain safety safeguards; there is no Settings control that disables semantic authority checks.
Bring your own keys
Section titled “Bring your own keys”Genie does not bundle model usage. Provider billing, quotas, retention, and account policy remain with the provider you configure. The free version of Genie and Coding Access describe Genie product access, not third-party model charges.
Web search and dictation
Section titled “Web search and dictation”Provider-native web search is available only on routes that actually support it. Genie does not add a fake web-search tool to unsupported providers. Dictation may use provider-backed audio when supported or the macOS speech path.
Custom / Local
Section titled “Custom / Local”Use Custom / Local when your server exposes an OpenAI-compatible API. Confirm the exact base URL, model ID, authentication convention, and tool-calling support. A successful connection test proves reachability and basic compatibility, not that every model supports native tool use or structured script work.