Apodex-1.1-mini

1. Model Introduction

Apodex-1.1 is a reasoning-first model for complex, long-horizon research tasks. Beyond searching and writing reports, it works directly with files, data, code, and tools to complete tasks from input to verifiable deliverables. Powered by AgentOS and an asynchronous Agent Team, it can maintain task state, adapt its plan, coordinate parallel work, and incorporate user feedback throughout execution.

Online Service

Try Apodex at apodex.ai.

Key Features

• End-to-end execution in real environments. Apodex 1.1 works directly with papers, datasets, spreadsheets, images, and code. It can clean data, select methods, run analyses, inspect intermediate results, recover from errors, and turn raw inputs into verifiable deliverables within one continuous task.
• Adaptive and user-steerable Agent Team. The model dynamically decomposes complex tasks and coordinates multiple Subagents working in parallel. Results flow continuously into a shared task state, allowing Apodex to revise priorities, preserve completed work, and respond to new files, requirements, or user feedback without restarting the entire task.
• Verification built into delivery. Statement Review independently checks key claims against their supporting sources, data, and computations before delivery. When evidence is insufficient, citations do not match, or results conflict with expectations, the system flags the issue, corrects the affected conclusion, and keeps the review process inspectable.

2. Evaluation Results

To prevent potential information leakage (e.g., retrieving benchmark answers from public repositories), we block access to relevant benchmark-hosting websites during evaluation.

Apodex 1.1 Agent Team delivers frontier-level performance across professional work, finance, scientific research, and general reasoning, achieving 38.5 on APEX-Agents, 78.8 on GDPVal, 54.3 on FrontierFinance, 63.3 on FrontierScience-Research, 35.3 on BioMysteryBench, and 56.1 on Humanity’s Last Exam. It consistently improves over the ReAct setup across all six benchmarks and achieves the highest scores among the compared systems on FrontierFinance and FrontierScience-Research.

Apodex-1.1-mini remains competitive with frontier models, leading FrontierFinance with 50.2 and nearly matching the best result on APEX-Agent with 27.7. Its Agent Team setup also consistently outperforms ReAct across all three benchmarks. You can try Apodex-1.1-mini with our Agent Team harness.

3. Quick Start

Apodex follows the Qwen3.5 chat template — tool calls are emitted as and reasoning as .... Launch with the matching parsers so the server returns standard OpenAI-style tool_calls and reasoning_content fields.

3.1 Deployment

We recommend deploying Apodex with the latest SGLang for an OpenAI-compatible endpoint.

SGLANG_ENABLE_SPEC_V2=1 python -m sglang.launch_server \
  --model-path apodex/Apodex-1.1-mini-NVFP4 \
  --quantization modelopt_mixed --moe-runner-backend flashinfer_trtllm \
  --tp-size 1 \
  --tool-call-parser qwen3_coder \
  --reasoning-parser qwen3 \
  --speculative-algorithm NEXTN --speculative-num-steps 3 \
  --speculative-eagle-topk 1 --speculative-num-draft-tokens 4 \
  --speculative-draft-model-quantization unquant \
  --mamba-scheduler-strategy extra_buffer \
  --mem-fraction-static 0.85 --context-length 262144 --language-only

3.2 Best Practices

For optimal performance in agentic tasks, we recommend:

temperature: 1.0
top_p: 0.95
repetition_penalty: 1.05
max_context_length: 262144
max_tokens: 32768

3.3 Agentic Usage

Apodex is trained for native function calling — tool schemas are passed via the tools= parameter of the chat-completions API and rendered into the prompt by the chat template, so the system prompt itself only needs to set the role and the high-level objective. We recommend the prompt below (this is the prompt used in our internal evaluation runs):

You are Apodex, an AI assistant developed by Apodex AI.

Apodex is the flagship agent of Apodex AI. Rather than a conventional conversational LLM, it is a general-purpose solver designed for mission-critical tasks.

Current time: {today_date}. In this environment you have access to a set of tools you can use to answer the user's question.

You only have access to the tools provided. You can use multiple tools per message, and will receive the results of those tools in the user's next response. You use tools step-by-step to accomplish a given task.

# General Objective

You accomplish a given task iteratively, breaking it down into clear steps and working through them methodically.

Substitute {today_date} with the current date (e.g. 2026-06-01). Do not inline tool descriptions in the system prompt — pass them via tools= so the Qwen3.5 chat template can emit the correct `` format and the server-side qwen3_coder parser can recover structured tool_calls for you.

The example below runs Apodex as a tool-using agent against an OpenAI-compatible endpoint (the SGLang / vLLM server launched above). The agent loops — executing the requested tools and feeding results back as role="tool" messages — until the model produces a final answer with no tool calls.

Before running, set the endpoint:

export OPENAI_API_KEY="EMPTY"           # any non-empty string for local servers
export BASE_URL="http://localhost:1234/v1"

import json
import os
from datetime import date
from openai import OpenAI

# -------- 1. Tool implementations --------
def get_weather(location: str, unit: str = "celsius") -> str:
    """Get current weather information for a city (simulated)."""
    table = {
        "London":   {"temperature": 15, "condition": "sunny",  "humidity": 45},
        "New York": {"temperature": 20, "condition": "cloudy", "humidity": 60},
        "Tokyo":    {"temp