Some details on what happened: A recent Chrome and Edge update tightened CORS (Cross-Origin Resource Sharing) enforcement for browser extensions. So requests made from Copyfish’s content scripts are now treated as coming from the page’s origin (e.g. https://some-website.com) rather than the extension. But the OCR API servers weren’t configured to allow arbitrary page origins, thus the error. Now the OCR API header includes Access-Control-Allow-Origin: * and the Copyfish extension works again.