diff --git a/How-reCAPTCHA-v3-Scoring-Works.md b/How-reCAPTCHA-v3-Scoring-Works.md
new file mode 100644
index 0000000..ab1e1f6
--- /dev/null
+++ b/How-reCAPTCHA-v3-Scoring-Works.md
@@ -0,0 +1,39 @@
+The developer API is designed to mirror the request format of the major CAPTCHA-solving services. What this means, scripts and scripts that currently call other services are able to point at CapSkip with little more than a URL change and no new code.
+
+Selenium remains a go-to for browser automation, and CapSkip drops into it cleanly. You keep the WebDriver logic unchanged and hand off the CAPTCHA to CapSkip when one appears, so the run keeps going without human input.
+
+Data control has become a genuine issue when every challenge gets shipped to a third-party service. Because CapSkip runs locally, nothing leaves your machine, so sensitive workflows remain contained. For regulated work, that is often the deciding factor.
+
+Web scraping is one of the most common use cases teams reach for a [Captcha Automation Tool](http://Gogs.9981.tech/kurtsilvestri/capskip5917/wiki/Running+Reliable+Automations+that+Handle+CAPTCHAs) solver. A single blocked request can halt an entire job, so clearing challenges automatically keeps throughput predictable. CapSkip fits such workflows neatly.
+
+Data control is a genuine issue when every challenge gets shipped to a remote service. With CapSkip, nothing leaves your machine, so private workflows remain contained. For sensitive data, this is often the clincher.
+
+A short migration checklist makes the switch smooth: repoint the API URL at CapSkip, confirm some live solves, then cut over production. Since the API matches major services, the bulk of the work is essentially done.
+
+Cloudflare Turnstile has become a common barrier on sites that aim to block bots and skip traditional image puzzles. CapSkip clears Turnstile locally within seconds, handling the challenge and managed modes. If you run automation that run into Turnstile, that takes away a major roadblock.
+
+A migration plan makes the move smooth: point your API URL at CapSkip, confirm a few real solves, then cut over the main jobs. Because the API matches major services, the bulk of the work is already done.
+
+Teams migrating from 2Captcha often expect a painful switch. In reality, because CapSkip mirrors the familiar API, the move comes down to largely a matter of the endpoint plus keeping the rest the same.
+
+Within reason, CAPTCHA solving supports legitimate use cases such as QA, monitoring, and permitted data collection. Always worth respecting each target's terms and relevant rules; used that way, a good solver is a productivity tool.
+
+Fundamentally, a CAPTCHA solver reads a challenge and returns the answer a site is looking for, so an automated tool can keep going. The difference with CapSkip is that the work stays on your own Windows machine - no challenge data leaves your hardware, and you avoid per-CAPTCHA fees. This mix of privacy and predictable cost is a real advantage for serious automation.
+
+GeeTest challenges are famously tricky for automation, which is why having a tool that covers them is a real plus. CapSkip solves GeeTest locally, so scripts that rely on those targets keep running when the puzzle shows up.
+
+Fundamentally, a CAPTCHA solver reads a challenge and returns the solution a site expects, so an automated tool can keep going. The difference with CapSkip is the work stays on your own Windows machine - no challenge data leaves your hardware, and you avoid per-solve fees. That combination of privacy and flat pricing is a real advantage for serious workloads.
+
+Google reCAPTCHA v2 remains one of the most common challenges on the web, from the classic checkbox to silent and callback variants. CapSkip handles all of these locally in seconds, which means your scraper will not stall whenever one appears. Because it emulates popular solver APIs, wiring it in tends to be painless.
+
+Web scraping is among the most common use cases people adopt a CAPTCHA solver. A single blocked request will halt an entire run, so solving challenges on the fly lets the pipeline predictable. CapSkip fits these pipelines cleanly.
+
+Fundamentally, a CAPTCHA solver interprets a challenge and produces the answer a site expects, so an automated script can keep going. What sets CapSkip apart is that everything happens locally - nothing is shipped off to a stranger, and there are no per-solve charges. That combination of privacy and flat pricing turns out to be a real advantage for steady workloads.
+
+The developer API was built to mirror the endpoints of the major CAPTCHA-solving services. What this means, tools and scripts that currently call other services can switch to CapSkip needing little more than a URL change and no new code.
+
+QA engineers hit CAPTCHAs too, especially when testing staging environments that mirror production. Rather than skipping these tests, teams are able to let CapSkip clear the challenge so coverage stays intact.
+
+A major advantages of processing on your own hardware comes down to cost. Traditional services charge per solve, so your bill rise as throughput grows. CapSkip uses fixed pricing and unlimited solves, so scaling does not mean worrying about the meter.
+
+Those "prove you're human" checks show up on almost every form, and they can stop any automated process in its tracks. Fortunately, a dedicated solver clears them automatically, and CapSkip does it on your own machine.
\ No newline at end of file