decision-machine-1 (milliseconds.ai)
Closed decision API · by milliseconds.ai (Baptiste Laget) · API endpoint saw sealed item text
JevBench v1.4.2.2 score
39.9
Rank #25 of 91 ranked systems.
23.4 points behind Jev 1.13.0's 63.3.
Published axes
- intelligence
- 41.3
- calibration
- 68.3
- speed
- 92.9
- cost
- 53.7
Against Jev 1.13.0
Four radars compare this fixed pair across the score axes, accuracy per tier, and accuracy by family on the hard tier and sealed set. Further out is better on every spoke.
- A: decision-machine-1 — Closed decision API · Score 39.9 (#25)
- B: Jev 1.13.0 — Jev (TypeSafe, closed) · Score 63.3 (#4)
The four score axes
Accuracy per tier, incl. sealed
Current question set by family (hard + sealed)
Sealed set by family
Availability and evidence
- Openness
- Marked closed in the published row
- License note
- proprietary API, closed weights
- Cost evidence
- measured; the board’s row disclosure contains the published basis.
- Endpoint condition
- production API (milliseconds.ai, served from its nearest region), measured from Germany
- Note on this row
- A closed-weights decision model behind a production API that serves TypeSafe's wire format, so the unchanged typesafe adapter ran it. Run on a free test key (30 requests a minute, 2.2 s between requests); the provider states the inference infrastructure is the same as for paid keys. Cost is the public paid tariff, $0.04 per million input tokens (output free), times the input tokens the API reported.
- Published source
- https://www.milliseconds.ai
From the public v1.4.2.2 aggregate. Scores and ranks can change when a new release is published.
Read the full board and published method. The overall score is a composite, not raw accuracy.