To use a model hosted on HuggingFace, specify the huggingface.co path in the from field and, when needed, the files to include.
fromThe from key takes the form of huggingface:model_path. Below shows 2 common example of from key configuration.
huggingface:username/modelname: Implies the latest version of modelname hosted by username.huggingface:huggingface.co/username/modelname:revision: Specifies a particular revision of modelname by username, including the optional domain.The from key follows the following regex format.
The from key consists of five components:
huggingface:.huggingface.co/ immediately after the prefix. Currently no other Huggingface compatible services are supported.org)./, the model name (model).:) followed by the git-like revision identifier (revision).nameThe model name. This will be used as the model ID within Spice and Spice's endpoints (i.e. http://localhost:8090/v1/models). This can be set to the same value as the model ID in the from field.
params| Param | Description | Default |
|---|---|---|
hf_token | The Huggingface access token. | - |
model_type | The architecture to load the model as. Supported values: mistral, gemma, mixtral, llama, phi2, phi3, qwen2, gemma2, starcoder2, phi3.5moe, deepseekv2, deepseekv3 | - |
tools | Which [tools] should be made available to the model. Set to auto to use all available tools. | - |
system_prompt |
filesThe specific file path for Huggingface model. For example, GGUF model formats require a specific file path, other varieties (e.g. .safetensors) are inferred.
Access tokens can be provided for Huggingface models in two ways:
~/.cache/huggingface/token). Default.For more details on authentication, see access tokens.
:::warning[Limitations]
| An additional system prompt used for all chat completions to this model. |
| - |