Skip to main content

Overview

A profile sends each kind of AI work to its own route. Davinci decides which route a request uses; you decide which model sits on each route. Matching the class of model to the route matters more than any other setting for quality and cost. A frontier model on the Simple tool route spends heavily on work that runs constantly. A small model on the Complex tool route produces code and CAD that does not compile.

Routes At A Glance

For the routes where the choice is a trade between cost and quality, plot how hard the work is against how often it runs:
Chat is not plotted because users choose from every class. Reference analysis, Media analysis, Image generation, and Embedding are not plotted because the input or output type decides the model. Users pick their chat model from the choices the profile offers, so offer several across price points: a frontier model for hard problems, a mid-size model for everyday work, and a small model for quick questions. Davinci works with text-only chat models, but strongly prefer models with image input so the agent can see images in the conversation. The agent also calls tools from chat, so choose models with reliable tool calling and streaming even though the editor does not require them.
Media analysis runs only on a Google provider. Davinci uploads the file to the Gemini File API, so the provider must authenticate with an API key or environment variable. Media analysis on any other provider fails at runtime. Uploaded media leaves your deployment for Google’s service.

Example Models

Hosted models are listed by family, without version numbers. Providers release new versions often, so use the newest version of each family and confirm the exact model ID in the provider’s model list. The open-source column lists US open-weight models only. They run through an OpenAI-compatible, Ollama, LiteLLM, Groq, Cerebras, or OpenRouter provider. Every chat and tool model in the tables accepts image input except gpt-oss, which is marked text only.

Text And Tool Routes

Muse Spark Open is Meta’s frontier open-weight model: 816B total parameters with 42B active per token and a 1M-token context window. Self-hosting it takes a multi-GPU server, so most deployments use it through a hosted platform such as Groq or OpenRouter. Its license has limited commercial terms. Other open-weight models trail hosted frontier models on the Complex route, so pair a self-hosted deployment with a hosted model there when policy allows.

Multimodal And Specialized Routes

Embedding Dimensions

The embedding offering’s vector dimensions must match the model’s output. Changing dimensions after vectors exist requires regenerating project vectors.

Tips For Choosing

  • Chat: offer three or four models across classes, preferably with image input, and mark the one most users should use day to day as the default. Put the most expensive frontier models in a higher profile when cost matters.
  • Open-weight tool calling: the serving stack must expose tool calling. For example, start vLLM with automatic tool choice and the model’s tool parser, or use an Ollama model that lists tool support. Confirm with verification before publishing.
  • Reasoning models: they add latency to every call. On the Simple route, prefer a non-reasoning model or set a low reasoning effort in the route’s generation defaults.
  • Context windows: Summarization and Reference analysis read long inputs. Pick models with large context windows for both.

Single-Vendor And Self-Hosted Setups

A profile can be published with only a default chat route and the three tool routes. Users of that profile cannot use any workload whose route is left empty, except Summarization, which falls back to the chat model.