GLiNER2.5-multi-Decide vs Fastino GLiDE
GLiNER2.5-multi-Decide and Fastino GLiDE have no measured difference in accuracy, calibration or cost in our data yet.
| Spec | GLiNER2.5-multi-Decide | Fastino GLiDE |
|---|---|---|
| Provider | Fastino | Fastino |
| Decision Index score | — | 60.2 |
| Calibration error (ECE) | — | 0.040 |
| Median latency (p50) | — | 98 ms |
| Cost per 1,000 decisions | — | $0.030 |
| Parameters | 287M | 28B |
| Open weights | Yes | No |
| Question types | Choice (one of N options), Score (ordered rubric), Yes / no, Extraction (typed spans) | Choice (one of N options), Score (ordered rubric), Yes / no |
| Mechanism | Span encoder (GLiNER family) | Hosted API |
| License | apache-2.0 | proprietary |
FAQ
Is GLiNER2.5-multi-Decide or Fastino GLiDE more accurate?
At least one of the two has no Jev Decision Index score yet, so their accuracy cannot be compared here.
Which is better calibrated, GLiNER2.5-multi-Decide or Fastino GLiDE?
No calibration difference between GLiNER2.5-multi-Decide and Fastino GLiDE is recorded yet.
Is GLiNER2.5-multi-Decide or Fastino GLiDE cheaper per 1,000 decisions?
A hosted price is not recorded for both models; open-weight models cost the compute you run them on.
Cost per 1,000 decisions assumes 200 input tokens per decision. Pricing is indicative — confirm with the provider before production use. Highlighted values indicate the better figure for that row.