mirror of
https://github.com/Routstr/routstr-core.git
synced 2026-10-05 20:28:23 +00:00
Jeroen UbbinkandClaude Opus 5
e202435ca0
A stored rate that is negative or non-finite is not a price, but every guard on the read path tested truthiness, and `NaN`, `inf` and a negative float are all truthy. Such a row was advertised in the catalog and built into the routing map, and the cost calculation cannot bill on it: every request on the model fell through to the flat maximum reservation, or — for a negative rate — was billed an amount settlement credits back to the caller. `has_usable_pricing` asks the question once, across every billable rate, so the served-catalog and routing backstops answer it identically. One unusable rate disqualifies the whole price: a positive completion rate must not hide a negative prompt rate. Zero is untouched — a free model is a real price. The admin listing (`include_disabled`) is deliberately exempt, or the operator would lose sight of the row that needs repairing. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_011cKHVF5LA7TR5QuYi6ErLM