Providers
BYOK providers and routing
Foreverse is built around bring-your-own-key (BYOK). This page documents the providers it speaks to, how keys are stored, and how request routing actually works. The visual provider matrix lives on the BYOK landing page; this is the long-form reference.
Supported providers
OpenAI, Anthropic, Google (Gemini and Vertex), Mistral, DeepSeek, xAI, Cohere, Groq, Together, Replicate, and Fireworks. Additional OpenAI-compatible providers are reachable through the generic compatible client.
Request routing
BYOK requests leave your device with the model name you picked, the encrypted key for that provider, and the chapter context Foreverse assembled. There is no Foreverse-managed proxy for BYOK by default. Responses stream back into the reader.
- Per-scene model selection is shown next to every continuation.
- Provider host and API version come from the provider record; Foreverse does not guess the path.
- Streaming uses the provider's native SSE format where supported.
Key storage
- Encrypted on device using the platform's secure preferences.
- Not synced across devices unless you opt in to a future managed sync.
- Not echoed back in logs, telemetry, or screenshots.
Official channel
Foreverse also offers an optional official channel for image, TTS, and video generation, billed in Foreverse credits. The official channel is clearly labelled in the reader as official, separate from BYOK. It is opt-in and never replaces a BYOK route silently.
Revoke and rotate
Open Settings > Providers, find the provider, and remove or replace the key. Existing branches keep their model record but will require a new key for further requests.