Skip to main content
Model provider extensions connect AgentScope Java to hosted or local chat model APIs. Each provider can be selected through a ModelRegistry id when its extension module is on the classpath.

modelId format and matching rules

<providerId>:<modelName> is the recommended canonical form (for example dashscope:qwen-max); actual routing follows these matching rules: Provider prefixes follow the module list below (openai:, openai-official:, deepseek:, glm:, kimi:, minimax:, dashscope:, gemini:, anthropic:, ollama:). When a model id cannot be resolved, the error message lists the provider ids actually installed on the classpath. modelId here is the registry routing vocabulary. It is distinct from modelIdentity, the resolution input of ModelRegistry.resolve (composite contextId@modelId or bare modelId) — see ModelRegistry and ModelCreationContext.