DeepSeek Harness · run failure
dsh run failed: “pricing not configured for provider/model”
503 "pricing not configured for provider/model"
The provider returned 503 with “pricing not configured for provider/model”. Unlike a normal 5xx, this one is about configuration, not availability.
provider 返回了 503 并附带「pricing not configured for provider/model」。与普通的 5xx 不同，这一条讲的是配置，不是可用性。
Why it happens根因
The provider has no pricing entry for the model route the request used, so it refuses to serve it. This is the signature of a model switch: the route exists, but the billing metadata behind your key does not cover the new model. On a measured corpus this class appeared only on the single day a new model shipped, alongside auth and unsupported-model failures — 8 of 14 turns failed that day against a 3.7% baseline.
provider 没有为本次请求使用的模型路由登记计价信息，因此拒绝服务。这是「切模型」的典型指纹：路由存在，但你这把 key 背后的计费元数据不覆盖新模型。在一份实测语料里，这一类只出现在新模型上线的那一天，并与 auth、unsupported model 的失败同时出现——那天 14 个 turn 里失败 8 个，而基线只有 3.7%。
How to fix it怎么修
- Pick a model whose route has pricing configured for this key, or complete the route’s configuration first.
- If you just switched models, switch back — that restores service immediately and confirms the cause.
- When several classes appear on the same day (auth, unsupported model, pricing), treat it as one configuration event, not three separate bugs.
npx dsh-why run see every run failure this can name看它能定性的全部运行期失败- 选一个这条 key 的路由已配置计价的模型，或先把该路由的配置补完。
- 如果刚切过模型，先切回去——这能立刻恢复服务，也确认了原因。
- 当同一天出现多个类别（auth、unsupported model、pricing）时，把它们当作一次配置事件，而不是三个独立的 bug。
npx dsh-why run see every run failure this can name看它能定性的全部运行期失败Is this my plugin’s fault?这是我的插件引起的吗？
No. This is a local configuration state, not code. Nothing in your plugin set can set or unset a credential.
不是。这是本地配置状态，不是代码问题。你装的任何插件都无法设置或取消一个凭证。
Related failures相关失败
400 "unsupported model"the route cannot serve it401: The API Key appears to be invalid or may have expiredthe key was rejectedclient-modules: require("…") missed the module table— or the other way round: dsh will not start at all
400 "unsupported model"路由不提供这个模型401: The API Key appears to be invalid or may have expiredkey 被拒绝client-modules: require("…") missed the module table—— 或者反过来：dsh 根本起不来
FAQ常见问题
Is a 503 “pricing not configured” a provider outage?
No. An outage returns a generic 5xx that affects everyone; this returns a specific configuration message and affects the routes that lack pricing metadata.
Why did this start right after I changed models?
The new model is served by a route your key’s billing configuration does not yet cover. dsh-why groups same-day failures so this shows up as one event instead of a mystery.
503「pricing not configured」是 provider 故障吗？
不是。故障返回的是影响所有人的通用 5xx；这一条返回的是明确的配置信息，影响的是缺计价元数据的那条路由。
为什么我刚换模型就开始报这个？
新模型由一条你这把 key 的计费配置尚未覆盖的路由提供服务。dsh-why 会把同一天的失败归组，所以它会表现为一次事件，而不是一团谜。