SubQ Snap (preview, SubQ)
Data: JevBench v1.6.39, published 2026-10-22
Capability 81.5 · API offering, ranked on the API leaderboard
Last measured: 2026-10-13 · measurement release: v1.6.17
Proprietary hosted API (no weights release)
intelligence
72.3
calibration
90.7
speed
86.4
cost
57.7
Composite (secondary)
74.4 · Not ranked on this board
Cost and measurement conditions
$0.026 per 1,000 decisions (estimated)
Operator's own published standard usage tariff: USD 0.05 per 1M INPUT tokens with no output billing. Two vendor sources, both snapshotted: the pricing section of https://subq.ai/ read on 14 Oct 2026 08:10Z ('In $0.05 per 1M tokens Input / Out Free Output') and the vendor's own launch post 'Introducing SubQ Snap' ('SubQ Snap is priced at $0.05 per million input tokens, with no charge for output tokens'), which also dates the tariff to the product's launch; Subquadratic's Alexander Whedon separately confirmed the figure in writing to Florian on 14 Oct 2026 01:16 Berlin (board #19133). Counted under interpretation I-1 (a manufacturer's standard, non-promotional launch list price counts from day 1 - the reading that already admitted kushal-gemma4-31b-it-autoloops). DISCLOSED: Snap is in a capacity-limited public preview - first come, first served, with a waitlist once capacity is reached - so this is the vendor's stated usage price for a product that is not yet openly bookable by everyone; CoS deputy decision #19174 rules explicitly that I-1 covers this tariff during that public preview, on the condition that the capacity limit and waitlist are stated here, as they are. The same pricing section offers 'Free 100M tokens for the first 10,000 users': that is a promotional trial credit and is deliberately NOT used - a free tier is priced at the published paid tariff, never as cost 0. The tariff is multiplied by this row's OWN measured input tokens (1,943,705 over 1,500 answered rows, mean 1,296) and divided by the 1,485 items of the common cost basis the scorer uses. The output term is zero twice over: the tariff bills no output, and the vendor's own usage meter reports 0 output tokens on all 1,500 rows. Gate chain: CoS deputy #18975 made the cost axis conditional on a separate frozen-pricing change passing re-freeze, unchanged-row proof and independent review; the chief of staff asked for it in #19133; the scoped change adds this one key to pricing_v15.LAUNCH_LIST_PRICE_API and nothing else (r113/pricing/CANDIDATE.diff; unchanged-row proof r113/receipts/PRICING-EQUIV-R113.json and two rounds of independent review, r113/review-pricing/REVIEW.json (REVISE) and r113/review-pricing-r2/REVIEW.json (PASS); the findings about this row's text and the builder's gates are applied here, the two about the publication layer are on the build sheet). INSIDE THE OFFICIAL COST CAP on the common basis: USD 0.025716 per 1,000 decisions is 0.398x the official cap USD 0.064595. Over all 1,500 items the row cost USD 0.064790 (1.003x the cap) and was disclosed as ranked over the cap in v1.6.29; that disclosure is superseded. COMMON COST BASIS (v1.6.30): cost per 1,000 decisions is computed on the common 1,485 items of this draw, leaving out the 15 very long items (at least 76,358 input tokens as counted by the rows that answered them). They are the 15 items the Jev reference refused with max_tokens_exceeded, which the other rows that did not answer them refused or failed on; their tokens count for no row, whether the row refused or answered them, and a refused item still counts as a wrong answer for Intelligence. This row: USD 0.025716 per 1,000 decisions (0.398x the official cost cap USD 0.064595), against USD 0.064790 over all 1,500 items (v1.6.29).
p50 latency: 0.5 s
none (API)
Vendor-hosted api.subq.ai /v1/systemone API, model `subq-snap-preview`; latency measured from Sandy (Germany) on the official per-item latency subset without API adjustment. Full S1200+P300 draw of v1.6-regular-20261012 through the unchanged run_api_full_v161.py; the full-set exposure gate logged all 1,200 sealed items to provider `subq` before the first request (CoS deputy #18975; every sealed item of this draw was already retired). Native probabilities on all three question types, no generated tokens. Hosting implementation and deployed weights were not independently inspected. Florian's work order (X, 12 Oct 2026). SubQ retains API inputs indefinitely by default; acceptable only because this draw's items are already retired.