Model reference · open weights
Athene-Agent is an open-weight language model from Nexusflow. Athene-V2-Agent (BF16) weighs 145 GB; the smallest configuration that runs it is 4× L40S 48 GB.
Summary of the Nexusflow/Athene-V2-Agent model card, 2026-10-01
What it is
| Released by | Nexusflow |
|---|---|
| Released | 2024-11-12 |
| Parameters | 72.7B |
| VRAM | 145 GB for the weights |
What it runs on
| Card | Requests at once | Context max | Memory | |
|---|---|---|---|---|
| 8K each | 32K each | |||
| RTX 3060 12 GB … H200 141 GB 11 smaller cards | — | — | — | |
| B200 180 GB | 8 | 2 | all 32K | 176 GB |
| 4× L40S 48 GB tensor parallel | 9 | 2 | all 32K | 44.0 GB a card |
| 2× RTX PRO 6000 Blackwell 96 GB tensor parallel | 11 | 2 | all 32K | 93.8 GB a card |
| 2× H200 141 GB tensor parallel | 44 | 11 | all 32K | 138 GB a card |
| 4× H100 80 GB tensor parallel | 53 | 13 | all 32K | 78.1 GB a card |
| 4× A100 80 GB tensor parallel | 60 | 15 | all 32K | 78.2 GB a card |
| 2× B200 180 GB tensor parallel | 71 | 17 | all 32K | 176 GB a card |
| Requests at once | 8K tokens each | 32K tokens each |
|---|---|---|
| 1 | 149 GB | 157 GB |
| 5 | 160 GB | 200 GB |
| 8 | 168 GB | 232 GB |
| 16 | 189 GB | 318 GB |
| 32 | 232 GB | 490 GB |
| 64 | 318 GB | 834 GB |
One card, with vLLM's small-card settings.
From the model card
Athene-V2-Agent is an open-source Agent LLM that surpasses the state-of-the-art in function calling and agentic capabilities.
💪 Versatile Agent Capability: Athene-V2-Agent is an agent model, capable of operating in environments with deeply nested dependencies with the environment. It is capable of reasoning and doing planning for trajectories with many tool calls necessary to answer a single query.
📊 Performance Highlights: Athene-V2-Agent surpasses GPT-4o in single FC tasks by 18% in function calling success rates, and by 17% in Agentic success rates.
🔧 Generalization to the Unseen: Athene-V2-Agent has never been trained on the functions or agentic settings used in evaluation.
Athene-V2-Agent is usable in any OpenAI API-compatible environment using our VLLM docker image. This should be a simple "drop-in" replacement to any agentic or tool-use setting with our VLLM docker image.
docker run --name athene-v2-agent \
--runtime nvidia --gpus '"device=0,1,2,3,4,5,6,7"' \
-v ~/.cache/huggingface:/root/.cache/huggingface \
--env "HUGGING_FACE_HUB_TOKEN=" \
-p :8000 \
--ipc=host \
ghcr.io/nexusflowai/athene-v2-vllm:latest \
--model Nexusflow/Athene-V2-Agent \
--dtype=auto \
--tensor-parallel-size=8 \
--enable-auto-tool-choice \
--tool-call-parser Athene-V2-Agent
You can now submit any OpenAI-Compatible tool-use requests to the model by hitting the VLLM endpoint. Athene-V2-Agent will be able to issue tool calls that you can execute and return results for.
WARNING: Athene-V2-Agent uses a CUSTOM prompting style that is baked into the custom docker image, as the executable calls are extracted from the model's generated planning. For best performance, please ensure to use the docker image above for Athene-V2-Agent, including when benchmarking the model. Using HuggingFace tokenizer's chat template will yield suboptimal results for Agent usecases. Please reach out to us on Discord if you run into any issues!
An example Weather agent for this can be found here: Link. This example includes handling Athene for queries that are answerable and not answerable by the current tools.
An example extraction and RAG-Agent can be found here: Link. This example includes handling RAG-based queries with a wikipedia tool.
The Athene-V2-Agent model is strongly tuned to have its behavior be controllable with tools to make it easy to integrate into systems.
Therefore, the model won't by default reject queries that are out of domain, as it will try its best to issue the most relevant call. However, when expecting irrelevant user queries and wanting the model to reject them, you can use a no-op function. For example, something like this would work:
{
"type": "function",
"function" : {
"name": "no_relevant_function",
"description": "Call this when no other provided function can be called to answer the user query.",
"parameters": {
"type": "object",
"properties": {
"user_query_span": {
"type": "string",
"description": "The part of the user_query that cannot be answered by any other function calls."
}
},
"required": ["user_query_span"]
}
}
}
Please see the example Link here for a demo of this.
Since Athene-V2-Agent model is strongly tuned to be controllable, so we wanted to ensure that it does not chat unless explicitly instructed to do so.
You can do this by adding a chat tool, and allowing it to do so in the system prompt:
{
"type": "function",
"function": {
"name": "chat",
"description": "Call this tool when you want to chat with the user. The user won't see anything except for whatever you pass into this function. You can use this tool to ask for more information when insufficient information is presented, and to send the final results back to the user.",
"parameters": {
"type": "object",
"properties": {
"chat_string": {
"type": "string",
"description": "The chat message to send to the user to chat back to them.",
}
},
"required": ["chat_string"],
},
},
}
And the following system prompt, as an example (but feel free to experiment to make Athene-V2-Agent behave the way you want it to!):
{"role" : "system", "content" : "You can use the chat tool to ask the user for more information, and to send the final results."},
Please see the example Link here for a demo of this.
Quoted from the model card on Hugging Face. The full card is behind the Hugging Face link above.