OpenRouter now rejects management keys from the browser on both
/api/v1/keys and /api/v1/analytics/query, so the management-key flow can
no longer work in the extension. Read the configured key's own usage from
GET /api/v1/key instead, which returns UTC daily, weekly, and monthly
buckets and works from the browser.
Drop the key-type selection, key listing/selection, pagination, and the
management/analytics endpoints. Validate the key against /key before
persisting, and write a fresh record so legacy keyType/keyIds fields are
dropped. Keep the browser-block hint for anyone still storing a
management key.
Extension pages with host permissions are treated as same-origin, so the
target origin's cookies rode along on every request. OpenRouter's
Clerk-protected analytics endpoint then tried to read the management key in
the Authorization header as a session JWT and answered 403, breaking the
spend total on the dashboard.
Default the shared fetch to credentials "omit" (still overridable per call),
and surface OpenRouter's own error message for failed requests instead of a
generic status summary.