Instructions to use nex-agi/Nex-N2-mini with libraries, inference providers, notebooks, and local apps. Follow these links to get started.
- Libraries
- Transformers
How to use nex-agi/Nex-N2-mini with Transformers:
# Use a pipeline as a high-level helper from transformers import pipeline pipe = pipeline("text-generation", model="nex-agi/Nex-N2-mini") messages = [ { "role": "user", "content": [ {"type": "image", "url": "https://huggingface.co/datasets/huggingface/documentation-images/resolve/main/p-blog/candy.JPG"}, {"type": "text", "text": "What animal is on the candy?"} ] }, ] pipe(text=messages)# Load model directly from transformers import AutoProcessor, AutoModelForMultimodalLM processor = AutoProcessor.from_pretrained("nex-agi/Nex-N2-mini") model = AutoModelForMultimodalLM.from_pretrained("nex-agi/Nex-N2-mini") messages = [ { "role": "user", "content": [ {"type": "image", "url": "https://huggingface.co/datasets/huggingface/documentation-images/resolve/main/p-blog/candy.JPG"}, {"type": "text", "text": "What animal is on the candy?"} ] }, ] inputs = processor.apply_chat_template( messages, add_generation_prompt=True, tokenize=True, return_dict=True, return_tensors="pt", ).to(model.device) outputs = model.generate(**inputs, max_new_tokens=40) print(processor.decode(outputs[0][inputs["input_ids"].shape[-1]:])) - Notebooks
- Google Colab
- Kaggle
- Local Apps Settings
- vLLM
How to use nex-agi/Nex-N2-mini with vLLM:
Install from pip and serve model
# Install vLLM from pip: pip install vllm # Start the vLLM server: vllm serve "nex-agi/Nex-N2-mini" # Call the server using curl (OpenAI-compatible API): curl -X POST "http://localhost:8000/v1/chat/completions" \ -H "Content-Type: application/json" \ --data '{ "model": "nex-agi/Nex-N2-mini", "messages": [ { "role": "user", "content": "What is the capital of France?" } ] }'Use Docker
docker model run hf.co/nex-agi/Nex-N2-mini
- SGLang
How to use nex-agi/Nex-N2-mini with SGLang:
Install from pip and serve model
# Install SGLang from pip: pip install sglang # Start the SGLang server: python3 -m sglang.launch_server \ --model-path "nex-agi/Nex-N2-mini" \ --host 0.0.0.0 \ --port 30000 # Call the server using curl (OpenAI-compatible API): curl -X POST "http://localhost:30000/v1/chat/completions" \ -H "Content-Type: application/json" \ --data '{ "model": "nex-agi/Nex-N2-mini", "messages": [ { "role": "user", "content": "What is the capital of France?" } ] }'Use Docker images
docker run --gpus all \ --shm-size 32g \ -p 30000:30000 \ -v ~/.cache/huggingface:/root/.cache/huggingface \ --env "HF_TOKEN=<secret>" \ --ipc=host \ lmsysorg/sglang:latest \ python3 -m sglang.launch_server \ --model-path "nex-agi/Nex-N2-mini" \ --host 0.0.0.0 \ --port 30000 # Call the server using curl (OpenAI-compatible API): curl -X POST "http://localhost:30000/v1/chat/completions" \ -H "Content-Type: application/json" \ --data '{ "model": "nex-agi/Nex-N2-mini", "messages": [ { "role": "user", "content": "What is the capital of France?" } ] }' - Docker Model Runner
How to use nex-agi/Nex-N2-mini with Docker Model Runner:
docker model run hf.co/nex-agi/Nex-N2-mini
Deceptive Model Card
This is a deceptive model card which portrays this model as original work when it is a fine-tune of Qwen 3.5.
The model tree does not show it as a finetune and the only mention of the fact is buried 2/3 of the way down the page where most people will miss it.
Additionally, no comparison is made to the model it was fine tuned from, to even show any improvement which was made from the base model.
Thank you for your feedback. We would like to clarify that this was never our intention. We respect and appreciate the work of the Qwen team and the broader open-source community. This project is built on top of existing open-source contributions, and we are also open-sourcing our own work in the hope of supporting further community collaboration, not diminishing or overlooking upstream contributions.
For reference, here are some benchmark comparison results:
| Benchmark | Nex-N2-Pro | Qwen3.5-397B-A17B | Qwen3.7-Max |
|---|---|---|---|
| BrowseComp | 83.7 | 69.0/78.6 | β |
| WideSearch | 75.6 | 74.0 | β |
| SWE-Bench Verified | 80.8 | 76.4 | 80.4 |
| IFEval | 94.0 | 92.6 | 94.3 |
| SWE-Pro / SWE-bench Pro | 58.8 | β | 60.6 |
| GPQA Diamond | 90.7 | β | 92.4 |
| Apex | 36.5 | β | 44.5 |
| WildClawBench | 53.5 | 36.5 | - |
| Benchmark | Nex-N2-Mini | Qwen3.5-35B-A3B | Qwen3.6-35B-A3B |
|---|---|---|---|
| BrowseComp | 74.1 | 61.0 | β |
| WideSearch | 62.0 | 57.1 | 60.1 |
| SWE-Bench Verified | 74.4 | 69.2 | 73.4 |
| SWE-Bench Pro | 50.2 | β | 49.5 |
| TAU3 / TAU3-Bench | 65.9 | β | 67.2 |
| GPQA Diamond | 82.6 | 84.2 | β |
| IFEval | 89.1 | 91.9 | β |
This is a deceptive model card which portrays this model as original work when it is a fine-tune of Qwen 3.5.
The model tree does not show it as a finetune and the only mention of the fact is buried 2/3 of the way down the page where most people will miss it.
Additionally, no comparison is made to the model it was fine tuned from, to even show any improvement which was made from the base model.
They said this is a qwen finetune right in the benchmark text, where 99% of the people go straight to, it would be a very bad place to put it if they want to hide it.
Also this is finetuned on a BASE model, not on an instruct model. How are you going to compare the benchmark of a base model and this instruct finetune?