Model Providers Reference

Agent steps run against an AI provider. This page lists the built-in provider catalog shared by Shipfox installations. It includes each provider ID, support status, compatible harnesses, and default model. For a setup walkthrough, see Agent Setup.

Shipfox Cloud also supplies the managed shipfox provider. See Shipfox Cloud models for its available models and exact IDs.

Supported providers

Each provider is configured per workspace with its credentials. The default model is used when an agent step names the provider but not a model. A step fails when it selects a provider that is not compatible with its harness.

Provider	provider ID	Default model	Compatible harnesses
Anthropic	anthropic	claude-opus-5	pi, claude
Ant Ling	ant-ling	Ring-2.6-1T	pi
Azure OpenAI	azure-openai-responses	gpt-5.6-sol	pi
Baseten	baseten	zai-org/GLM-5.2	pi
OpenAI	openai	gpt-5.6-sol	pi
DeepSeek	deepseek	deepseek-v4-pro	pi
NVIDIA	nvidia	nvidia/nemotron-3-ultra-550b-a55b	pi
Google AI Studio	google	gemini-3.1-pro-preview	pi
Mistral	mistral	mistral-large-latest	pi
Groq	groq	openai/gpt-oss-120b	pi
Cerebras	cerebras	gpt-oss-120b	pi
Cloudflare AI Gateway	cloudflare-ai-gateway	claude-opus-5	pi
Cloudflare Workers AI	cloudflare-workers-ai	@cf/moonshotai/kimi-k2.7-code	pi
xAI	xai	grok-4.6	pi
OpenRouter	openrouter	anthropic/claude-opus-5	pi
Vercel AI Gateway	vercel-ai-gateway	anthropic/claude-opus-5	pi
Z.ai	zai	glm-5.3	pi
Z.ai Coding CN	zai-coding-cn	glm-5.3	pi
OpenCode	opencode	claude-opus-5	pi
OpenCode Go	opencode-go	kimi-k3	pi
Hugging Face	huggingface	deepseek-ai/DeepSeek-V4-Pro	pi
Fireworks	fireworks	accounts/fireworks/models/deepseek-v4-pro	pi
Together AI	together	deepseek-ai/DeepSeek-V4-Pro	pi
Kimi Coding	kimi-coding	k3-256k	pi
Qwen Token Plan	qwen-token-plan	qwen3.8-max	pi
Qwen Token Plan CN	qwen-token-plan-cn	qwen3.8-max	pi
Qwen Token Plan Individual	qwen-token-plan-individual	qwen3.8-max	pi
MiniMax	minimax	MiniMax-M3	pi
MiniMax CN	minimax-cn	MiniMax-M3	pi
Moonshot AI	moonshotai	kimi-k3	pi
Moonshot AI CN	moonshotai-cn	kimi-k3	pi
Xiaomi	xiaomi	mimo-v2.5-pro	pi
Xiaomi Token Plan CN	xiaomi-token-plan-cn	mimo-v2.5-pro	pi
Xiaomi Token Plan AMS	xiaomi-token-plan-ams	mimo-v2.5-pro	pi
Xiaomi Token Plan SGP	xiaomi-token-plan-sgp	mimo-v2.5-pro	pi

Custom model providers are workspace-specific, so they do not appear in this table. They are compatible with the pi harness. Use Add a custom provider to connect one.

Selecting a model

The model you set on an agent step is passed to the provider and validated against that provider's available models: an unrecognized model ID fails the step with a clear error. Each provider's full model list comes from the provider's own catalog. The default model above is what Shipfox picks when you omit model.

How configuration works

Providers are configured per workspace. For each provider you configure, you supply its credentials and can optionally set a default model and mark one provider as the workspace default. Credentials are stored securely. Shipfox stores their encrypted values and never returns the raw secrets through settings or management APIs. A runner receives the decrypted credential bundle only for its leased agent step. Configuration takes effect immediately. No redeploy is needed.

Resolution and defaults

When an agent step runs, Shipfox resolves the harness, provider, model, and thinking level in this order:

• Harness: the step's harness, else the pinned harness of an existing named session the step continues, else the workspace default harness, else pi.
• Provider: the step's provider, else a compatible workspace default provider, else anthropic.
• Model: the step's model, else the configured default model for the resolved provider, else that provider's catalog default (the table above).
• Thinking: the step's thinking, else the provider's configured default, else xhigh.

So an agent step with a prompt alone runs on the workspace default harness, provider, and model. Naming a provider but no model uses that provider's default model.

Unsupported providers

Related pages