How to bypass aggressive forced CAPTCHA on a dynamic academic repository (CUHK)?

[HarideP]

Hi everyone,

I am building an automated scraper for an academic repository (https://repository.lib.cuhk.edu.hk/en/collection/etd/year), which structures resources by year. However, we've hit a hard block.

Here is the situation:

1. Aggressive CAPTCHA: The site uses a mandatory CAPTCHA (image verification) system that triggers for almost every visit, regardless of whether it's a real human browser or a bot.
2. AI/Agent Failure: Our automated agents attempted to solve the image verification multiple times but were consistently blocked.
3. JS-Heavy: The site is heavily reliant on JavaScript to load the actual item lists, making simple HTTP requests (requests/curl) useless.

My Questions:

1. What is the state-of-the-art stack for bypassing such aggressive image CAPTCHAs in a fully automated Python pipeline today? (e.g., combining undetected-chromedriver with a specific solver service?)
2. Since this is an academic repository, it likely supports OAI-PMH. Does anyone have experience bypassing the frontend completely by finding standard API endpoints (like /oai/request) on similar library systems?
3. Any specific configuration recommendations for browser automation to reduce the CAPTCHA difficulty/frequency on this specific type of site?

Thanks in advance for any insights!

[VeNoMouS]

What is the CAPTCHA provider? reCaptcha? or hCaptcha? or a self baked solution?

EDIT

Sorry , you provided a URL, it looks like its going to awswaf... the solution itself isnt that hard to get around , obviously time and effort , i havent, personally tried to do this myself... ive never seen it before, you could either

a) find a 3rd party that solves this for you
b) reverse engineer and solve it yourself

looking at the payload, i think the images are the "client solution" , and the rest will be part of the javascript , it could be easy if there is no javascript vm... but yea would require investigation