GLiNER2.5-Decide vs vera-spark
vera-spark is more accurate on the Jev Decision Index, GLiNER2.5-Decide is better calibrated. Choose on whichever of accuracy, calibration and cost matters most for your decisions.
| Spec | GLiNER2.5-Decide | vera-spark |
|---|---|---|
| Provider | Fastino | scar-ai |
| Decision Index score | 10.1 | 11.0 |
| Calibration error (ECE) | 0.088 | 0.157 |
| Median latency (p50) | 23 ms | 80 ms |
| Cost per 1,000 decisions | — | — |
| Parameters | 486M | 638M |
| Open weights | Yes | Yes |
| 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) | Encoder classifier |
| License | apache-2.0 | apache-2.0 |
FAQ
Is GLiNER2.5-Decide or vera-spark more accurate?
vera-spark scores higher on the Jev Decision Index (11.0 vs 10.1).
Which is better calibrated, GLiNER2.5-Decide or vera-spark?
GLiNER2.5-Decide has the lower expected calibration error (0.088 vs 0.157), so its stated confidence is closer to how often it is right.
Is GLiNER2.5-Decide or vera-spark 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.