Your agent hits a CAPTCHA and the run stops. Resolvr is the layer that gets it moving again: send the challenge context to one endpoint, get back the token, browser identity headers or clearance cookies the next request needs. Every challenge is solved on real Chrome infrastructure loading the real page, so what comes back behaves like a browser, not a replayed string.

Solved today: recaptcha_v2 · recaptcha_v3 · cloudflare_turnstile · cloudflare_blockpage — more in active development.

Every docs page is markdown to an agent: append .md or send Accept: text/markdown, and llms.txt indexes them all. Hand your agent the prompt and it writes the integration.

Implement Resolvr support for recaptcha_v2, recaptcha_v3, cloudflare_turnstile, cloudflare_blockpage in this project using the Resolvr API docs:
https://resolvr.com/docs

Start from the docs index at https://resolvr.com/llms.txt and read the overview plus the page for each task type. Every page is served as markdown when you append .md to its URL or send Accept: text/markdown.

Follow this project's existing HTTP client, configuration, error-handling, naming and test patterns. Integrate directly with the Resolvr API without duplicating existing infrastructure.