Guides

Choose a model provider

Start with privacy, governance, and runtime constraints. Then open the canonical provider guide and select a model available to that account or local runtime.

Choose by constraint

Start with the decision you already know

Pick the operating constraint first. Choose a specific model only after the provider connection works, because model IDs, access, pricing, and limits change independently.

Start with the broadest hosted catalog

OpenRouter. One account gives you room to compare supported hosted model families before standardizing.

OpenRouter

Keep existing cloud governance

AWS, Azure, or Google Cloud. Use the identity, regional, networking, and billing controls your organization already operates.

AWS Bedrock · Azure AI Foundry · GCP Vertex AI

Use a direct model-provider account

Choose the provider your team already trusts. Direct integrations keep credentials, quotas, and support relationships with that provider.

OpenAI · DeepSeek · xAI Grok · Z.ai · Sakana AI · Cerebras · NVIDIA

Keep inference on hardware you control

Ollama, MLX, or llama.cpp. Local runtimes avoid a hosted model credential but make your team responsible for models and capacity.

Ollama · MLX · llama.cpp

Current integrations

Compare provider paths

Every row opens the canonical setup guide. No model IDs or prices are duplicated here.

Hosted providers

Use an account, cloud identity, or gateway credential.

OpenRouter Trying and switching among hosted model families through one account. OPENROUTER_API_KEY OpenAI Teams that want a direct OpenAI account and billing relationship. OPENAI_API_KEY AWS Bedrock Organizations already governing model access through AWS. AWS credentials or API key Azure AI Foundry Organizations using Azure identity, networking, and regional controls. Azure endpoint + credentials GCP Vertex AI Teams operating model access through a Google Cloud project. Google Cloud credentials DeepSeek Direct access to DeepSeek models through a compatible hosted API. DEEPSEEK_API_KEY xAI Grok Direct use of Grok models from an xAI account. XAI_API_KEY Z.ai Using GLM-family models through a compatible hosted endpoint. ZAI_API_KEY Sakana AI Accounts using supported Sakana AI orchestration models. SAKANA_API_KEY Cerebras Hosted inference through a Cerebras account. CEREBRAS_API_KEY NVIDIA Hosted model inference through NVIDIA services. NVIDIA_API_KEY LLMGateway Centralized routing, policy, caching, and observability for teams. LLMGATEWAY_API_KEY

Local runtimes

Keep inference on hardware you operate.

Ollama The quickest path to private local inference on common platforms. Ollama host MLX Private local inference optimized for Apple Silicon. Apple Silicon llama.cpp Portable, configurable GGUF inference on hardware you control. llama.cpp server

This directory is generated from the same provider manifest as the integrations directory.

Change scope safely

Switch models without rewriting setup

Session

Try a model now

Use /model inside an interactive session, then select a model exposed by the active provider.

Command

Override one run

Pass --model <model-id> when launching Autohand so the saved default remains unchanged.

Default

Standardize future runs

Set the provider and model in Autohand configuration only after the smallest verification prompt succeeds.

Before standardizing

Validate the choice against your workload

  1. 01
    Run a representative task

    Use code from the repository and workflow you actually plan to support.

  2. 02
    Measure the constraints that matter

    Record completion quality, latency, tool use, context handling, and cost or hardware load.

  3. 03
    Confirm production controls

    Review credential handling, data terms, quotas, regional availability, and fallback behavior.

Compare Autohand-hosted models Review provider configuration patterns Plan model cost controls