Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

OpenRouter sync records promotional prices as standard prices

オープン
  • 何か問題がありますか？
#4,580 コメント 2 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

  • #4576 @samtin0x による — マージされずにクローズ

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
30/100
issue の種類
バグ
明瞭さ
説明が足りない
活発さ
静か
技術スタック
typescript
領域
data

調査の方向性

issue、sync.md、および実装リファレンス #4576 に記載された OpenRouter エンドポイントルートから始めます。10 個の新しいテストと classifyAutoMerge の議論を確認し、その後、プロモーション価格と標準価格、保存するフィールド、churn、プロバイダーの対象範囲について求められている判断を解決します。完了とは、選択した動作がリグレッションなしでカバーされていることを意味します。

索引モデルが issue の本文から書いたものです。

説明

The catalog records promotional prices as if they were standard ones

GET /api/v1/models — the feed the OpenRouter sync reads — quotes a headline price that is already discounted when the route it came from is running a promotion. The payload has no field saying so, so the discount is invisible to the sync and the promo rate lands in the catalog as the model's price.

providers/openrouter/models/upstage/solar-pro4.toml is committed today as:

[cost]
input = 0.03
output = 0.12

That is a 90%-off promotion. The standard rate is $0.30 / $1.20. Nothing in the file records that, and when the promo ends the price will appear to jump 10x with no explanation in the diff.

This is provable from single-endpoint models, where there is no ambiguity about which route the headline price came from:

Model Endpoints discount In catalog Standard rate
upstage/solar-pro4 1 0.9 $0.03/M $0.30/M
inclusionai/ling-2.6-flash 1 0.9 $0.01/M $0.10/M
inclusionai/ring-2.6-1t 1 0.75 $0.075/M $0.30/M
meituan/longcat-2.0 1 0.6 $0.30/M $0.75/M
tencent/hy3-preview 1 0.65 $0.063/M $0.18/M

20 of the 350 OpenRouter models are currently affected.

Where the missing data lives

The per-model /api/v1/models/{author}/{slug}/endpoints route reports a discount fraction on each provider endpoint's pricing. OpenRouter also shows the pre-discount price struck through on the model's provider table — e.g. on deepseek-v4-flash-0731, StreamLake shows "35% off", $0.14 struck through, $0.091 charged.

The aggregate feed exposes neither.

Which discount belongs to the recorded price

The headline price does not say which endpoint it came from, which is the part that needs a decision. The rule that works: the endpoint quoting exactly the headline (prompt, completion) is the route being recorded, so its discount is the one consistent with the cost.input/cost.output already being written.

This matters because a model can have discounted endpoints that are not the one in the catalog. deepseek/deepseek-v4-flash-0731 has three discounted providers, but its headline $0.08/$0.252 is DigitalOcean's undiscounted row — so the correct answer for that model is no discount. Across all 350 models the rule produced zero ambiguous matches: 295 matched an undiscounted endpoint, 20 matched a discounted one, 10 matched none (all :free variants priced at 0).

Cost is one extra request per model; a full sweep is ~13s at a concurrency of 6.

Proposed shape

Keep prices meaning what they mean today — what you are billed — and add fields describing what has already been taken off them:

[cost]
input = 0.091      # billed
output = 0.182
discount = 0.35    # 35% off, already reflected above
input_list = 0.14  # standard rate
output_list = 0.28

*_list is price / (1 - discount), which is exactly the struck-through figure OpenRouter displays. It is derivable rather than new information, so it is a judgement call whether to store it — the argument for is that it makes the diff self-describing: when a promo ends, prices return to precisely the previously recorded input_list, distinguishing a promotion from a real price cut without recomputation.

Questions before this is worth merging

  1. Appetite. Is a promotional-price field in scope for what you want this dataset to be, or would you rather the catalog track standard rates only — in which case the fix is the inverse (record input_list as input) and this is still a bug worth closing.
  2. Store *_list, or just discount? The latter is smaller and loses nothing retrievable.
  3. Churn. A discount flips whenever a promo starts or ends. classifyAutoMerge gates on created/deleted counts and reasoning metadata — updated is computed but never gates anything, so discount-only changes would auto-merge unbounded. If that is unwanted it needs an update-side gate that does not exist today. (Measured over ~25 minutes none of the 20 moved, so the real rate may be low.)
  4. Scope. Wiring this for OpenRouter only leaves an authored discount on any other synced provider to be stripped on its next run, since those modules rebuild cost from their own APIs. Making it durable catalog-wide would need a runner-level preserve rule.

Implementation

#4576 implements the above for OpenRouter only, per sync.md's preference for small provider-specific PRs. Fail-soft (a model whose endpoint cannot be matched keeps its authored discount rather than churning), bun validate passes, 10 new tests, no regressions.

Happy to cut it down to just discount, rename the fields, or close it if this is out of scope — the decision on Q1 and Q2 changes what the PR should look like.

cc @rekram1-node @fwang

主要言語
TypeScript
スター
7.3k
フォーク
1.8k
平均マージ
1時間 32分
マージ済み PR（30日）
910

環境構築

このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

anomalyco/models.dev のほかの issue

anomalyco/models.dev の issue をすべて見る

似ている issue

TypeScript の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。