Skip to main content
A decision model evaluates text or structured application state against caller-defined outcomes and returns structured decisions—labels, probabilities, scores, and confidence—instead of generated prose. Use decision models when application code must classify an input, select a route, score against a rubric, moderate content, or decide whether an action should proceed.

​
Decision models vs. generative models

The two model types can work together. A decision model can classify a request, select an agent or model, or gate an action before a generative model produces an open-ended result.

​
Why use a decision model

  • Structured by construction — downstream code receives a bounded answer instead of prose that must be parsed.
  • Caller-defined outcomes — your application controls the permitted labels, routes, or levels.
  • Explicit uncertainty — probabilities and confidence let you automate clear cases and send ambiguous cases to a fallback or review path.

​
Explore Fastino decision models

GLiDE

Ask typed Noul, Choice, and Score questions against text or structured application state.

GLiNER 2.5 Decide

Run schema-defined, single-label or multi-label classification over English text.
To pull entities, relations, or structured records out of text, use GLiNER 2.5 Multi.

GLiNER 2.5 Multi

Extract entities, relations, and records from text in any supported language.