I would be careful framing that as a provider-detection bug. If a tool is driving subscription-only quota through an unsupported path, account blocks are a predictable enforcement boundary. The engineering fix is boring: make auth mode explicit in the client, show API-billed vs subscription-billed requests, warn before mixed modes, and keep retry/usage logs. Otherwise users diagnose a billing boundary as a model/tool failure.