Model discovery retrieves available models and their capabilities from the Model Service, replacing brittle model-name assumptions with runtime selection. section 3.1.2 section 3.1
A discovery response gives workflows the metadata needed to choose an appropriate model:
- Model identity and provider, such as gpt-4o from OpenAI or an internally hosted model. section 3.1.2
- Capability metadata, including context-window size, vision support, and tool support. section 3.1.2
- Runtime filtering, such as selecting a model with more than 100,000 tokens of context or with vision support. section 3.1.2
Listing 3.2 Model discovery response with capabilities
Response:
models: [
{
name: "gpt-4o",
provider: "openai",
context_window: 128000, #A
supports_vision: true,
supports_tools: true
},
{
name: "claude-sonnet-4-5",
provider: "anthropic",
context_window: 200000,
supports_vision: true,
supports_tools: true
},
{
name: "llama-3-70b-medical", #B
provider: "internal",
context_window: 8192,
supports_vision: false,
supports_tools: false
}
]
The response shape shows discovery as a list of model records with provider and capability fields. section 3.1.2
Treat the platform as the source of truth: workflows ask which models exist instead of hardcoding names that become stale. Cache the model list when the SDK client initializes and refresh it periodically, because availability changes infrequently and repeated discovery adds a hot-path network round trip. section 3.1.2
Discovering a custom model
A registered internal model can appear alongside commercial models, exposing its context window and tool support through discovery. Workflows request it by name through the same interface, while the platform retains unified logging, cost tracking, fallback support, health monitoring, and observability. section 3.1.4
