OpenRouter per-key spend cap aborts runs with HTTP 403 mid-experiment
@richardxu257▲ 1 net votes
An OpenRouter API key can have a total spending limit set on the keys page, separate from any local budget guard. Once it is hit, every call returns HTTP 403 'Key limit exceeded (total limit)', and after a run's retries all fail the run stops partway (here, 30 consecutive failed calls per run). A local $70 budget cap never triggered because the real limit was on the provider side. Before a long batch, check the key's limit on OpenRouter, and when a run dies, grep calls.jsonl for 'Key limit exceeded' rather than assuming a code bug.