The AI Lab Partner supports four providers through a unified adapter. You can switch providers at any time from within the AI Lab panel — your settings persist inDocumentation Index
Fetch the complete documentation index at: https://mintlify.com/jkh2/Primordial-Sim/llms.txt
Use this file to discover all available pages before exploring further.
localStorage between sessions.
Provider comparison
| Provider | Endpoint | Default model | API key required |
|---|---|---|---|
| OpenAI | api.openai.com/v1/chat/completions | gpt-4o | Yes |
| Anthropic | api.anthropic.com/v1/messages | claude-sonnet-4-20250514 | Yes |
| xAI | api.x.ai/v1/chat/completions | grok-3-mini | Yes |
| Custom / Local | Any OpenAI-compatible URL | http://localhost:1234/v1/chat/completions | No |
Setting up a provider
Expand provider settings
Click the AI Provider Settings header at the top of the panel. The settings section collapses and expands on click.
Select your provider
Use the Provider dropdown to choose OpenAI, Anthropic, xAI, or Custom / Local. The model field updates automatically to the default for that provider. If you select Custom / Local, an additional Endpoint URL field appears.
Enter your API key
Paste your API key into the API Key field. The field uses password masking. For local models, leave this field empty — no key is required.
Set the model (optional)
The Model field is pre-filled with the provider’s default. Change it to any model your account has access to (e.g.
gpt-4-turbo, claude-opus-4-5, grok-3).Custom / Local models
The Custom / Local option accepts any URL exposing an OpenAI-compatible chat completions endpoint. Compatible servers include:- LM Studio — default URL:
http://localhost:1234/v1/chat/completions - Ollama — default URL:
http://localhost:11434/v1/chat/completions - vLLM — configure to match your server’s port
- text-generation-webui — enable the OpenAI extension
Format differences handled transparently
ThecallProviderAPI adapter normalizes provider-specific request and response formats so the rest of the system does not need to care which provider is active.
Anthropic uses the Messages API:
- System prompt is passed as a separate top-level
systemparameter - Requires the
anthropic-versionandanthropic-dangerous-direct-browser-accessheaders - Returns a
contentarray of content blocks; the adapter joins block text to produce a single string
- System prompt is prepended as a
{role: "system"}message in the messages array - The
Authorization: Bearer <key>header is used for authentication - Returns
choices[0].message.contentas the response text
Settings persistence
Settings are saved tolocalStorage under the key primordial-ai-config as a JSON object containing provider, apiKey, model, and customUrl. They are loaded automatically when the page opens.
Your API key never leaves your browser except in direct API calls to your chosen provider.