Mindket

Drex DLM

Newversion 1 · updated

Overview

Scores yes or no, multiple choice and rating questions about a document in one pass, with a probability for every option. An 8B decision model from Nace.AI that you can run yourself, under a non-commercial license.

Drex DLM is a kit in the Business category, listed by Mindket. It is free. This is version 1, last updated on . Download it on this page, a zip of its files. Nothing in it runs by itself.

At a glance

You need
  • Python 3.12
  • git, to fetch the project's repository
  • About 16 GB of memory for the weights
Runs in
  • A Mac with Apple silicon, or a machine with an NVIDIA GPU
  • Python 3.12, the interpreter the card validated
  • Any client that speaks the System One request format
Start with
cd drex-decision-models
python3.12 -m venv .venv
source .venv/bin/activate

Platform

ServerRuns on it

About

What it is

Drex DLM is a decision model from Nace.AI. You hand it a document and a set of named questions, and it returns a probability for every option of every question. Each question can ask for yes or no, offer several choices or ask for a rating, and one forward pass scores them all. Its base is Efficient-DLM-8B from NVIDIA, a diffusion language model, with a light pointer head added on top.

Who it suits

It suits developers who need structured decisions from text, such as sorting support tickets, and who want to host the model themselves.

IndustryWho uses itHow they use itExample
Customer supportSupport leads and developersSort tickets by team, refund request and urgencyA double-charge ticket scored for billing, refund and urgency
Back officeOperations teamsTurn documents into typed answersAsk yes or no questions about a record
SoftwareDevelopersRun the same API as the hosted Drex service on their own machinePoint an existing client at a local server
ResearchApplied ML researchersStudy a diffusion language model with a pointer headCompare option probabilities across questions

If you need free text written back to you, or a license that allows commercial use, you can skip it.

Where to use it

The card says it was tested on Apple M5 Max and M5 Pro machines and on an NVIDIA H100 with CUDA, and that CPU-only use is untested.

  • A Mac with Apple silicon, or a machine with an NVIDIA GPU
  • Python 3.12, the interpreter the card validated
  • Any client that speaks the System One request format
Use caseWhoWhat they get back
Ticket triageSupport teamsProbabilities for the team, the refund question and urgency
Document questionsAnalystsTyped answers about a document, option by option
Local drop-in serverDevelopersThe same request format as the hosted API

How to set it up

You need Python 3.12, git, and roughly 16 GB of memory for the BF16 weights. Longer contexts and bigger batches need more memory.

  • Python 3.12
  • git, to fetch the project's repository
  • About 16 GB of memory for the weights
  1. Clone the project's repository from GitHub, as the card's quick start does.
  2. Create a virtual environment and install the requirements.
  3. Download the weights into the weights folder.
  4. Run the inference script on the sample request.
cd drex-decision-models
python3.12 -m venv .venv
source .venv/bin/activate
python -m pip install -r requirements.txt
hf download nace-ai/drex-dlm --local-dir weights/drex-dlm
python inference.py --model weights/drex-dlm --request examples/request.json

How to use it

The inference script shows the model's answers to the example support ticket. To serve the model instead, start the server script, then send it requests in the same format. The server has a health endpoint that reports ok once the weights are loaded.

python serve.py --model weights/drex-dlm --port 8000
{
  "state": {
    "ticket": "I was charged twice for the same order. Please refund the extra payment."
  },
  "questions": {
    "team": {
      "type": "choice",
      "instructions": "Which team should handle this ticket?",
      "criteria": {
        "billing": "Payments, charges, and refunds",
        "technical": "Bugs and outages",
        "other": "Anything else"
      }
    },
    "refund": {
      "type": "noul",
      "instructions": "Does the customer explicitly ask for a refund?"
    }
  }
}
ToolWhat it does
inference.pyPrints answers for a request file
serve.pyStarts a server on the port you choose
state fieldHolds the document, as a string, object or list
questions fieldHolds named questions, whose names return as keys of the answers

Example

You send the double-charge ticket with a question about which team should handle it and a yes or no question about a refund. The reply gives a probability for each team and for each refund answer.

For newcomers and experts

If you are new to this, think of it as a form that fills itself in with likelihoods. A first small step is to run the sample request from the quick start and read the printed answers.

If you know the field, the document gets bidirectional attention, and each question branch attends to the document and uses causal attention within itself. A shared pointer head turns decision and option-ending markers into queries and keys, and a scaled dot product, temperature and softmax give each question's probabilities. Larger requests are split across question rows.

  1. Document goes in as state
  2. Named questions branch from it
  3. One forward pass scores them
  4. Pointer head ranks each option
  5. A probability per option comes out

Good to know

The card lists a Q8_0 GGUF copy, forks of llama.cpp and Ollama, and an agent skill. It reuses the System One request format, which means existing tools built for that format need no changes.

Decision Index score reported on the card
Drex DLM52.31
Decider chat51.93
Jev51.67
AutoJev-27B50.94
Jebadiah 27B50.32
simple-jev50.21
  • License: cc-by-nc-4.0, which allows non-commercial use only
  • Cost to run: no API key or paid service is named, and the BF16 weights are about 16 GB
  • Data it reaches: the download comes from Hugging Face and GitHub, and a self-run server works on your own machine
  • Not for: commercial use, or CPU-only runs, which the card says it has not tested

README and files

README

Drex DLM

Scores yes or no, multiple choice and rating questions about a document in one pass, with a probability for every option. An 8B decision model from Nace.AI that you can run yourself, under a non-commercial license.

Made by nace-ai on Hugging Face. These notes are Mindket's, written from its model page and model card; the model's own files and license are on Hugging Face.

About

What it is: Drex DLM is a decision model from Nace.AI. You hand it a document and a set of named questions, and it returns a probability for every option of every question. Each question can ask for yes or no, offer several choices or ask for a rating, and one forward pass scores them all. Its base is Efficient-DLM-8B from NVIDIA, a diffusion language model, with a light pointer head added on top.

Who it suits: It suits developers who need structured decisions from text, such as sorting support tickets, and who want to host the model themselves.

Industry | Who uses it | How they use it | Example
Customer support | Support leads and developers | Sort tickets by team, refund request and urgency | A double-charge ticket scored for billing, refund and urgency
Back office | Operations teams | Turn documents into typed answers | Ask yes or no questions about a record
Software | Developers | Run the same API as the hosted Drex service on their own machine | Point an existing client at a local server
Research | Applied ML researchers | Study a diffusion language model with a pointer head | Compare option probabilities across questions

If you need free text written back to you, or a license that allows commercial use, you can skip it.

Where to use it: The card says it was tested on Apple M5 Max and M5 Pro machines and on an NVIDIA H100 with CUDA, and that CPU-only use is untested.

  • A Mac with Apple silicon, or a machine with an NVIDIA GPU
  • Python 3.12, the interpreter the card validated
  • Any client that speaks the System One request format
Use case | Who | What they get back
Ticket triage | Support teams | Probabilities for the team, the refund question and urgency
Document questions | Analysts | Typed answers about a document, option by option
Local drop-in server | Developers | The same request format as the hosted API

How to set it up: You need Python 3.12, git, and roughly 16 GB of memory for the BF16 weights. Longer contexts and bigger batches need more memory.

  • Python 3.12
  • git, to fetch the project's repository
  • About 16 GB of memory for the weights
  1. Clone the project's repository from GitHub, as the card's quick start does.
  2. Create a virtual environment and install the requirements.
  3. Download the weights into the weights folder.
  4. Run the inference script on the sample request.
cd drex-decision-models
python3.12 -m venv .venv
source .venv/bin/activate
python -m pip install -r requirements.txt
hf download nace-ai/drex-dlm --local-dir weights/drex-dlm
python inference.py --model weights/drex-dlm --request examples/request.json

How to use it: The inference script shows the model's answers to the example support ticket. To serve the model instead, start the server script, then send it requests in the same format. The server has a health endpoint that reports ok once the weights are loaded.

python serve.py --model weights/drex-dlm --port 8000
{
  "state": {
    "ticket": "I was charged twice for the same order. Please refund the extra payment."
  },
  "questions": {
    "team": {
      "type": "choice",
      "instructions": "Which team should handle this ticket?",
      "criteria": {
        "billing": "Payments, charges, and refunds",
        "technical": "Bugs and outages",
        "other": "Anything else"
      }
    },
    "refund": {
      "type": "noul",
      "instructions": "Does the customer explicitly ask for a refund?"
    }
  }
}
Tool | What it does
inference.py | Prints answers for a request file
serve.py | Starts a server on the port you choose
state field | Holds the document, as a string, object or list
questions field | Holds named questions, whose names return as keys of the answers

Example: You send the double-charge ticket with a question about which team should handle it and a yes or no question about a refund. The reply gives a probability for each team and for each refund answer.

For newcomers and experts: If you are new to this, think of it as a form that fills itself in with likelihoods. A first small step is to run the sample request from the quick start and read the printed answers.

If you know the field, the document gets bidirectional attention, and each question branch attends to the document and uses causal attention within itself. A shared pointer head turns decision and option-ending markers into queries and keys, and a scaled dot product, temperature and softmax give each question's probabilities. Larger requests are split across question rows.

Document goes in as state
Named questions branch from it
One forward pass scores them
Pointer head ranks each option
A probability per option comes out

Good to know: The card lists a Q8_0 GGUF copy, forks of llama.cpp and Ollama, and an agent skill. It reuses the System One request format, which means existing tools built for that format need no changes.

Title: Decision Index score reported on the card
Drex DLM: 52.31
Decider chat: 51.93
Jev: 51.67
AutoJev-27B: 50.94
Jebadiah 27B: 50.32
simple-jev: 50.21
  • License: cc-by-nc-4.0, which allows non-commercial use only
  • Cost to run: no API key or paid service is named, and the BF16 weights are about 16 GB
  • Data it reaches: the download comes from Hugging Face and GitHub, and a self-run server works on your own machine
  • Not for: commercial use, or CPU-only runs, which the card says it has not tested

On Hugging Face, 13 November 2026

  • Task: text classification
  • Library: transformers
  • Parameters: 8.2B
  • Weights: about 16.4 GB in BF16; about 4.1 GB at 4-bit (estimate)
  • Formats: Safetensors
  • Downloads in the last 30 days: 177
  • Likes: 25
  • License: cc-by-nc-4.0
  • Based on: nvidia/Efficient-DLM-8B
  • Quantized versions: 1
  • Tags: transformers, safetensors, edlm, feature-extraction, decision-model, system-one, typed-decisions, decision-index, classification, calibrated-probabilities, decisionbench, zero-shot

Links

Get the model

Download its files with Hugging Face's command line:

pip install -U huggingface_hub
hf download nace-ai/drex-dlm

Then follow the usage in its model card. Nothing in this kit runs by itself.

Files
README.md  7 KB

1 file, 7 KB, downloaded as a zip.

What’s new

  • Version 1 · 2026-11-13

Compare with similar

Listed Hugging Face models in the same category that share the most tags with this one.

ProductDownloads, last 30 daysLikesParametersLicenseLast change
Drex DLM This page177258.2Bcc-by-nc-4.0
basal-omni-1.0-ultraShares typed-decisions · classification · decision-model3,8314331.3Bapache-2.0
Amos 1 largeShares system-one · classification · decision-model69428—apache-2.0
H2O-Lightning-4BShares typed-decisions · decision-model · transformers10,5301074.7Bapache-2.0
pplx-decider-v1.1-27bShares classification · decision-model · safetensors4,06518226.1Bapache-2.0
NuExtract3Shares transformers · safetensors40,9153974.5Bapache-2.0
Numbers as Mindket last read them, on 2026-11-13.

Reviews

No ratings yet

Write a review

No reviews yet.

More from Mindket

See all from Mindket

anaksor-ocr

Sokheng · Kit

Reads Khmer and English text from documents, receipts and photos of signs, using a detector for text lines and a recogniser for each line. Suits developers who…

New

Qwen2.5-7B-Instruct as GGUF files in eight quantization sizes, to chat with locally through llama.cpp. For people who want a capable 7.6B model on their own co…

New

ACE-Step 1.5 XL SFT

ACE-Step · Kit

Generates music from text with a 4B diffusion decoder, 50 steps and guidance control, aiming for higher audio quality than the base. For creators with a GPU of…

New

Similar in Business

See all in Business

pplx-decider-v1.1-27b

perplexity-ai · Kit

Picks the best option for a decision from text and images, such as which team should handle a request, with a probability for each choice, for developers who b…

New

NuExtract3

numind · Kit

Reads documents as text or images and fills a JSON template with the fields you ask for, or converts the pages to Markdown. A 4B model for teams that process s…

New

Amos 1 large

mukaddamzaid · Kit

Answers typed questions about a case, given as text, JSON or a photo, in one pass with a probability for each allowed answer. A 27B decision model that writes…

New