ocx observe usage prices subscription lanes at API list rates, showing spend that never occurred #2711

Version measured: 2.28.0. Not re-verified at 2.33.0, though the open cost-metrics work (#1820, #2365) suggests this surface is active — filing as a correctness report, not a feature ask.

Summary

ocx observe usage multiplies subscription-lane tokens by API list prices and presents the result as a dollar figure. A subscription-billed lane (for example, a Claude subscription login routed native) has no per-token bill: the tokens are real, the dollars are not. The figure then aggregates alongside genuinely priced API-key lanes, so the total reads as spend that never occurred and cannot be reconciled against any invoice.

Expected

One of:

• subscription lanes reported with tokens but explicitly unpriced (the billing kind is known at attribution time), or
• the dollar figure labeled per-lane as a list-rate estimate that is not a bill, and excluded from any total that mixes billing kinds.

Failing toward not-pricing when the billing kind is undeclared would also be safer than defaulting to list rates.

What we do downstream

Our advisory usage reporter refuses to price subscription lanes at all and records the reason as policy (no-subscription-dollars in scripts/usage_report.py at https://github.com/Codeseys-Labs/agentic-sdlc: "a subscription turn is never priced, not even as an estimate; the gateway's own list-rate figure over subscription lanes is a defect ... and is never quoted here"). That protects our own report only; every other consumer of ocx observe usage still sees the phantom dollars.