Which AI connections does Lumstead support?
The preview supports provider API keys, managed AI through OpenRouter, and Ollama on a home server. A consumer chat subscription alone does not give Lumstead API access.
| Connection | How it connects | What to know |
|---|---|---|
| Managed AI | OpenRouter service connection | Prepaid USD balance; provider cost + 10% service fee. Owner payment setup required. |
| OpenRouter | Your API key | Use your provider balance and select an available model. |
| OpenAI | Your API key | API billing is separate from a ChatGPT subscription. |
| Anthropic | Your API key | Use an Anthropic API account. Claude subscription sign-in is not offered. |
| Z.ai | Your API key | Use the supported standard API connection. Plan-specific endpoints need separate validation. |
| Ollama | Model on your home server | In self-hosted mode, the server owner sets the address. Choose an installed model. Household tools require a model that supports tool calls. |
| Z.ai Coding Plan | Unavailable | A plan can connect only after Lumstead is approved as a supported tool. Standard API access is separate. |
| ChatGPT plan | Unavailable | An approved partner integration and its configuration are required. No connection is active. |
A key is not a subscription.
Consumer chat plans and developer API accounts are different products. Connect only with the method the provider permits. Lumstead does not ask for a Claude session cookie, browser token, or consumer account password.
ChatGPT supports approved partner connections under its own rules. Lumstead has no approved, configured partner connection in this build. Its connection entry remains a visible setup state. Use an OpenAI API key for available API access.
Connect only what helps.
Modules provide narrow tools for film history, home devices, wellness, notes, and finances. A disabled module removes its tools and screens for your account while keeping saved records. Some modules need an external credential, such as a film catalog token; enabling a module does not configure that service.
Home devices use direct supported protocols. Local setup and real hardware checks remain necessary. Cloud private-device control needs a local connector, which is not included yet. Use a local deployment for device control. The app shows whether a connection is configured and available.
Review the data path.
Your selected AI provider receives the question and selected context. Module services receive the information needed for their operation. API keys stay on the server. A successful connection check proves access; it does not guarantee answer quality or correct device behavior.