|
105 | 105 | "openai/gpt-5.6-luna-pro": ((1.00, 6.00, 0.10, 1.250), (0.10, 0.60, 0.01, 0.125)), |
106 | 106 | # Z.ai cut GLM 5.2 ~10% in the same week, unrelated to OpenAI. |
107 | 107 | "z-ai/glm-5.2": ((0.7966, 2.5036, 0.14794, None), (0.7168, 2.2528, 0.13312, None)), |
| 108 | + # Google halved Gemini 3.6 Flash some time after the 2026-08-01 snapshot; |
| 109 | + # found on 2026-08-13 while pricing 3.7 Flash. Every component moved by |
| 110 | + # exactly 0.5, so it is expressible. The runs themselves confirm the "was" |
| 111 | + # vector: least squares over the 299 recorded runs implies $1.34/$7.56, |
| 112 | + # which is $1.50/$7.50 with cache reads pulling the input average down. |
| 113 | + # |
| 114 | + # This one matters beyond its own row. Both Gemini entries are priced at the |
| 115 | + # google-ai-studio standard endpoint, and 3.7 Flash lists at the same |
| 116 | + # $0.75/$3.75 there, so without the revision the newer model would appear to |
| 117 | + # cost half what its predecessor does when the two are in fact identical. |
| 118 | + "google/gemini-3.6-flash": ((1.50, 7.50, 0.15, 0.08333333333333334), |
| 119 | + (0.75, 3.75, 0.075, 0.04166666666666667)), |
108 | 120 | } |
109 | 121 |
|
110 | 122 |
|
@@ -562,7 +574,52 @@ def run_cost(run): |
562 | 574 | {"specs": ["google/gemini-3.6-flash@max", "google/gemini-3.6-flash@xhigh", |
563 | 575 | "google/gemini-3.6-flash@high", "google/gemini-3.6-flash@medium", |
564 | 576 | "google/gemini-3.6-flash@low", "google/gemini-3.6-flash@minimal"], |
565 | | - "label": "Gemini 3.6 Flash", "lab": "Google", "open_weight": False}, |
| 577 | + # deprecated 2026-08-13: superseded by Gemini 3.7 Flash; charts carry one bar |
| 578 | + # per family's best (David). Unlike the Grok 4.5 retirement the same day, |
| 579 | + # this pair is not a tie that needed a tiebreak: 87.9 against 73.2 is a gap |
| 580 | + # of 14.7 on a combined half-width of 8.6, and 3.7 is also 3.3x cheaper per |
| 581 | + # task and 4.7x faster. Its 299 runs stay in main.jsonl as the audit trail. |
| 582 | + "label": "Gemini 3.6 Flash", "lab": "Google", "open_weight": False, |
| 583 | + "deprecated": True}, |
| 584 | + # Gemini 3.7 Flash, released and benchmarked 2026-08-13 (canonical slug |
| 585 | + # google/gemini-3.7-flash-20260813). Six endpoints, all status 0, but pinned |
| 586 | + # --provider-order google-ai-studio regardless: Gemini thought signatures only |
| 587 | + # validate on the endpoint that issued them, and AI Studio was both the faster |
| 588 | + # half at probe time (144 tok/s p50 against Vertex's 88) and the one billing |
| 589 | + # the undiscounted list price. Vertex carries a 50% launch discount, and |
| 590 | + # scoring a permanent row against a promotion is the defect the flex-tier note |
| 591 | + # above already rules out. The runs confirm the pin landed: least squares over |
| 592 | + # them implies exactly $0.75/$3.75. 234 runs, 0 errors, 0 retries. |
| 593 | + # |
| 594 | + # Probe: @disabled is a 400, "Reasoning is mandatory for this endpoint and |
| 595 | + # cannot be disabled", so @low is the floor. OpenRouter advertises low/medium/ |
| 596 | + # high and defaults to medium; @xhigh and @max are unadvertised, accepted, and |
| 597 | + # land INSIDE @high's band. Median first-call output on the two hard probe |
| 598 | + # tasks is 2.7k at low against 8.9k / 7.1k / 9.2k at high / xhigh / max: a |
| 599 | + # 3.3x step up from the floor, then 1.30x across the top three. Two real |
| 600 | + # levels, so neither unadvertised tier was swept, the same call Grok 4.6's |
| 601 | + # @max got. |
| 602 | + # |
| 603 | + # The dial is inert on the index, and the tiers trade one component for |
| 604 | + # another rather than climbing: SCI 87.9 / 85.0 / 87.5 at low / medium / high, |
| 605 | + # every pair overlapping, while one-shot goes 71 -> 65 -> 83% and pays for the |
| 606 | + # top end in cost (77 -> 58) and speed (100 -> 90). Correctness is 100% at all |
| 607 | + # three, 156/156. Note @medium, the provider default, is the WORST of the |
| 608 | + # three rather than the middle: at n=26 it read as the midpoint of a monotone |
| 609 | + # climb, and only the top-up to n=52 broke that. That is why the top-up went |
| 610 | + # to all three tiers instead of the nominal winner, and it is the argument for |
| 611 | + # doing so whenever a bracket lands inside its own error bar. |
| 612 | + # |
| 613 | + # The MCP cells are the cleanest noise measurement in the dataset. At @low and |
| 614 | + # @medium the model called assist_with_cairo ZERO times across 52 runs, so |
| 615 | + # those cells differ from baseline only by an unused tool definition sitting |
| 616 | + # in the prompt -- and they still moved -5.4 and +3.4. That is the n=26 error |
| 617 | + # bar with the mechanism held at zero, not behaviour, and it is the scale at |
| 618 | + # which every small lift in this study should be read. Only @high touches the |
| 619 | + # tool at all, 0.42 calls/run over 7 of 26 runs, for +0.6. |
| 620 | + {"specs": ["google/gemini-3.7-flash@low", "google/gemini-3.7-flash@medium", |
| 621 | + "google/gemini-3.7-flash@high"], |
| 622 | + "label": "Gemini 3.7 Flash", "lab": "Google", "open_weight": False}, |
566 | 623 | {"specs": ["openai/gpt-5.6-luna-pro", "openai/gpt-5.6-luna@max", |
567 | 624 | "openai/gpt-5.6-luna@xhigh", "openai/gpt-5.6-luna@high", |
568 | 625 | "openai/gpt-5.6-luna@medium", "openai/gpt-5.6-luna@low", |
|
0 commit comments