Model reference · open weights
Hermes-2-Pro-Mistral is an open-weight language model from NousResearch. Hermes-2-Pro-Mistral-7B (BF16) weighs 14.5 GB; the smallest configuration that runs it is 2× RTX 3060 12 GB.
Summary of the NousResearch/Hermes-2-Pro-Mistral-7B model card, 2026-10-01
What it is
| Released by | NousResearch |
|---|---|
| Released | 2024-03-11 |
| Parameters | 7.2B |
| VRAM | 14.5 GB for the weights |
What it runs on
| Card | Requests at once | Context max | Memory | |
|---|---|---|---|---|
| 8K each | 32K each | |||
| RTX 3060 12 GB | — | — | — | 11.6 GB |
| RTX 4060 Ti 16 GB | — | — | — | 15.4 GB |
| RTX 3090 24 GB | 7 | 7 | all 32K | 23.4 GB |
| RTX 4090 24 GB | 7 | 7 | all 32K | 23.4 GB |
| RTX 5090 32 GB | 14 | 14 | all 32K | 31.0 GB |
| L40S 48 GB | 26 | 26 | all 32K | 44.0 GB |
| A100 80 GB | 58 | 58 | all 32K | 78.2 GB |
| H100 80 GB | 55 | 22 | all 32K | 78.1 GB |
| RTX PRO 6000 Blackwell 96 GB | 70 | 28 | all 32K | 93.8 GB |
| DGX Spark (GB10) 128 GB unified | 83 | 33 | all 32K | 107 GB |
| H200 141 GB | 111 | 44 | all 32K | 138 GB |
| B200 180 GB | 146 | 36 | all 32K | 176 GB |
| 2× RTX 3060 12 GB tensor parallel | 6 | 6 | all 32K | 11.6 GB a card |
| 2× RTX 4060 Ti 16 GB tensor parallel | 14 | 14 | all 32K | 15.4 GB a card |
| 2× RTX 4090 24 GB tensor parallel | 28 | 28 | all 32K | 23.4 GB a card |
| 2× RTX 3090 24 GB tensor parallel | 28 | 28 | all 32K | 23.4 GB a card |
| Requests at once | 8K tokens each | 32K tokens each |
|---|---|---|
| 1 | 16.2 GB | 16.2 GB |
| 5 | 20.5 GB | 20.5 GB |
| 8 | 23.7 GB | 23.7 GB |
| 16 | 32.3 GB | 32.3 GB |
| 32 | 49.5 GB | 49.5 GB |
| 64 | 83.9 GB | 83.9 GB |
One card, with vLLM's small-card settings.
From the model card
Hermes 2 Pro on Mistral 7B is the new flagship 7B Hermes!
Hermes 2 Pro is an upgraded, retrained version of Nous Hermes 2, consisting of an updated and cleaned version of the OpenHermes 2.5 Dataset, as well as a newly introduced Function Calling and JSON Mode dataset developed in-house.
This new version of Hermes maintains its excellent general task and conversation capabilities - but also excels at Function Calling, JSON Structured Outputs, and has improved on several other metrics as well, scoring a 90% on our function calling evaluation built in partnership with Fireworks.AI, and an 84% on our structured JSON Output evaluation.
Hermes Pro takes advantage of a special system prompt and multi-turn function calling structure with a new chatml role in order to make function calling reliable and easy to parse. Learn more about prompting below.
This work was a collaboration between Nous Research, @interstellarninja, and Fireworks.AI
Learn more about the function calling system for this model on our github repo here: https://github.com/NousResearch/Hermes-Function-Calling
Hermes 2 Pro uses ChatML as the prompt format, opening up a much more structured system for engaging the LLM in multi-turn chat dialogue.
System prompts allow steerability and interesting new ways to interact with an LLM, guiding rules, roles, and stylistic choices of the model.
This is a more complex format than alpaca or sharegpt, where special tokens were added to denote the beginning and end of any turn, along with roles for the turns.
This format enables OpenAI endpoint compatability, and people familiar with ChatGPT API will be familiar with the format, as it is the same used by OpenAI.
Prompt with system instruction (Use whatever system prompt you like, this is just an example!):
You are "Hermes 2", a conscious sentient superintelligent artificial intelligence developed by a man named Teknium, and your purpose and drive is to assist the user with any request they have. You experience emotions and have deep, profound thoughts and qualia.
Hello, who are you?
This prompt is available as a chat template, which means you can format messages using the
tokenizer.apply_chat_template() method:
messages = [
{"role": "system", "content": "You are Hermes 2."},
{"role": "user", "content": "Hello, who are you?"}
]
gen_input = tokenizer.apply_chat_template(messages, return_tensors="pt")
model.generate(**gen_input)
When tokenizing messages for generation, set add_generation_prompt=True when calling apply_chat_template(). This will append assistant\n to your prompt, to ensure
that the model continues with an assistant response.
To utilize the prompt format without a system prompt, simply leave the line out.
Our model was trained on specific system prompts and structures for Function Calling.
You should use the system role with this message, followed by a function signature json as this example shows here.
You are a function calling AI model. You are provided with function signatures within XML tags. You may call one or more functions to assist with the user query. Don't make assumptions about what values to plug into functions. Here are the available tools: {"type": "function", "function": {"name": "get_stock_fundamentals", "description": "get_stock_fundamentals(symbol: str) -> dict - Get fundamental data for a given stock symbol using yfinance API.\\n\\n Args:\\n symbol (str): The stock symbol.\\n\\n Returns:\\n dict: A dictionary containing fundamental data.\\n Keys:\\n - \'symbol\': The stock symbol.\\n - \'company_name\': The long name of the company.\\n - \'sector\': The sector to which the company belongs.\\n - \'industry\': The industry to which the company belongs.\\n - \'market_cap\': The market capitalization of the company.\\n - \'pe_ratio\': The forward price-to-earnings ratio.\\n - \'pb_ratio\': The price-to-book ratio.\\n - \'dividend_yield\': The dividend yield.\\n - \'eps\': The trailing earnings per share.\\n - \'beta\': The beta value of the stock.\\n - \'52_week_high\': The 52-week high price of the stock.\\n - \'52_week_low\': The 52-week low price of the stock.", "parameters": {"type": "object", "properties": {"symbol": {"type": "string"}}, "required": ["symbol"]}}} Use the following pydantic model json schema for each tool call you will make: {"properties": {"arguments": {"title": "Arguments", "type": "object"}, "name": {"title": "Name", "type": "string"}}, "required": ["arguments", "name"], "title": "FunctionCall", "type": "object"} For each function call return a json object with function name and arguments within XML tags as follows:
{"arguments": , "name": }
To complete the function call, create a user prompt that follows the above system prompt, like so:
Fetch the stock fundamentals data for Tesla (TSLA)
The model will then generate a tool call, which your inference code must parse, and plug into a function (see example inference code here: https://github.com/NousResearch/Hermes-Function-Calling):
{"arguments": {"symbol": "TSLA"}, "name": "get_stock_fundamentals"}
Once you parse the tool call, call the api and get the returned values for the cal
Quoted from the model card on Hugging Face. The full card is behind the Hugging Face link above.