Skip to main content

Overview

SkyDiscover supports any OpenAI-compatible API endpoint. Provider-specific configurations are handled automatically based on model name prefixes.

Supported Providers

OpenAI

GPT-4, GPT-5, o1, o3, o4 models

Google Gemini

Gemini 2.0, 3.0 models

Anthropic

Claude 3.5, 3.7, 4.0 models

DeepSeek

DeepSeek-V3, DeepSeek-Coder

Mistral

Mistral Large, Codestral

Local Models

Ollama, vLLM, any OpenAI-compatible

OpenAI

Setup

Configuration

Supported Models

  • gpt-5 (latest GPT-5)
  • gpt-4o, gpt-4o-mini
  • o1, o1-mini, o1-pro
  • o3, o3-mini
  • o4, o4-mini

Reasoning Models (o1/o3/o4)

For o-series models, set reasoning effort:

Google Gemini

Setup

Configuration

Supported Models

  • gemini/gemini-3-pro (Gemini 3.0 Pro)
  • gemini/gemini-3-flash (Gemini 3.0 Flash)
  • gemini/gemini-2.0-flash-exp
The gemini/ prefix is required for auto-detection. SkyDiscover strips it before sending to the API.

Anthropic Claude

Setup

Configuration

Supported Models

  • claude-3-7-sonnet
  • claude-3-5-sonnet
  • claude-4-opus (when available)

DeepSeek

Setup

Configuration

Supported Models

  • deepseek-chat (DeepSeek-V3)
  • deepseek-coder

Mistral

Setup

Configuration

Azure OpenAI

Setup

Configuration

Local Models

Ollama

1

Install Ollama

2

Pull a Model

3

Configure SkyDiscover

Or via CLI:

vLLM

1

Install vLLM

2

Start vLLM Server

3

Configure SkyDiscover

LM Studio

1

Install LM Studio

Download from lmstudio.ai
2

Load a Model

Search and download Qwen/Qwen2.5-Coder-32B-Instruct-GGUF
3

Start Local Server

In LM Studio: Local Server → Start Server (default port 1234)
4

Configure SkyDiscover

Multiple Providers

Mix and match providers in a single run:
SkyDiscover samples models proportionally to their weights.

Model-Specific Settings

Per-Model Parameters

Custom Client Initialization

For advanced use cases, pass a custom LLM client:

Provider Auto-Detection

SkyDiscover automatically detects providers from model names:

Override Detection

Use provider/model syntax or explicit api_base:

API Key Priority

SkyDiscover resolves API keys in this order:
  1. Per-model config:
  2. Provider environment variable:
  3. Generic OPENAI_API_KEY:
Always set provider-specific keys when using multiple providers to avoid auth errors.

Troubleshooting

Error: 401 UnauthorizedFix:
  1. Check your API key is correct
  2. Verify the key is exported: echo $OPENAI_API_KEY
  3. Ensure provider-specific key is set (e.g., GEMINI_API_KEY for Gemini)
  4. Try hardcoding the key in config temporarily to isolate the issue
Error: Connection refused or Failed to connectFix:
  1. Check server is running: curl http://localhost:11434/v1/models
  2. Verify port matches config
  3. For Ollama: ollama serve should show “Listening on 127.0.0.1:11434”
  4. For vLLM: Check logs for startup errors
Error: The model 'xyz' does not existFix:
  1. For Ollama: ollama list to see available models
  2. For cloud providers: Check spelling and model availability
  3. Verify provider prefix: gemini/gemini-3-pro not just gemini-3-pro
Error: 429 Too Many RequestsFix:
  1. Reduce max_parallel_iterations in config
  2. Add retry delay: retry_delay: 10
  3. Use multiple API keys with separate model entries
  4. Switch to local models for unlimited requests

Best Practices

Use Environment Variables

Never commit API keys. Use env vars or .env files.

Mix Local and Cloud

Use cheap local models for exploration, cloud models for exploitation.

Set Timeouts

Increase timeout for large models or slow servers.

Monitor Costs

Use gpt-4o-mini or local models during development.

Next Steps

Configuration

Full LLM configuration reference

Running Discovery

Start your first discovery run