ZeroPoint scores options against an implicit none state on a CPU. Read its bundled model, short input budgets and saved missing-option tests.
By Javier Marín · First published package release; October catch-up: 31 Oct 2026
A CPU decision model that scores supplied options against a fixed zero-energy none state. It packages an encoder derived from multilingual-e5-small, ONNX weights and a fitted head. Its runtime sorts options into a canonical order before scoring, so order consistency belongs to the complete serving path.
Quick answers
What is ZeroPoint by Javier Marín?
ZeroPoint: A CPU decision model that scores supplied options against a fixed zero-energy none state.
Reads 192 text word pieces and 16 per option, with truncation flags; options processed in blocks of 20
Access
Bundled model files; Python with NumPy, ONNX Runtime and tokenizers
Licence
Apache-2.0 code; upstream multilingual-e5-small is MIT, with notices
Claims and sources
The maker reports 53.6% correct decisions including none across 900 matched cases, half with no right option, versus 58.6% for Strands Decider 2B v1. ZeroPoint takes a 42 ms median on a two-core CPU with two threads; Strands uses an NVIDIA L4 in that comparison. These timings do not compare raw speed on the same hardware. vendor reportedsource
Scores option labels and an implicit none state using a bundled ONNX encoder and fitted head. The maker publishes saved comparisons, model hashes and fitting code. Canonical option sorting and one-case inference are part of its consistency recipe. The 900-case matched comparison reports 53.6% correct including none, with half the cases having no right option. Short input budgets and truncation flags remain explicit.