# KagedCap

> A CAPTCHA-solving API for AI agents and automated workflows. One HTTP endpoint accepts a
> reCAPTCHA challenge and returns a solved token, so an agent running sanctioned work does not
> stall at a bot check. Prepaid balance, billed per successful solve. Operated by
> KageSolutions LLC.

KagedCap exists for automation the operator is authorized to run: QA and test automation on
your own properties, accessibility flows, uptime and content monitoring, authorized data
access, and internal workflow automation. Challenges meant to stop abusive bots cannot
distinguish that work from abuse, and the run dies at the challenge.

It is not for evading security controls, breaking a site's terms, credential stuffing, fraud,
or bulk account creation. Accounts used for abuse are suspended under the Terms.

## What it does

- Supported: reCAPTCHA v2, reCAPTCHA v3, reCAPTCHA v3 Enterprise, and ProxyLess variants of
  the v3 tasks (no proxy required).
- Request: `POST /solve` with a JSON body naming the task, the page URL and the sitekey.
  `action` is optional on every reCAPTCHA task — supplying it binds a v3 token to your
  site's action; omitting it performs a no-action solve. Response returns `success`, the
  `token`, and a `score` where the site exposes one.
- Proxy is optional per task type. ProxyLess tasks must omit it; non-ProxyLess tasks require it.
- Billing is per successful solve against a prepaid balance. Failed solves are not billed.
- Every solve is logged to the account that made it and visible in the dashboard.
- High-volume customers can run on dedicated nodes rather than the shared fleet.

## Who it is for

- Teams building AI agents and browser-automation workflows that must not stall mid-run.
- QA and test-automation suites running against properties the team owns or is authorized to test.
- Accessibility, monitoring and internal automation blocked by a challenge.

## Guides

- [Why reCAPTCHA v3 stops your AI agent](https://kagedcap.io/guides/why-recaptcha-v3-stops-ai-agents):
  what v3 actually does to an automated session — it scores, it does not challenge — how to tell
  scoring from a rule or a different vendor's block, and the options in order (allowlist your own
  site first; a solver only for authorized work).
- [Handling reCAPTCHA in Playwright and Puppeteer](https://kagedcap.io/guides/recaptcha-playwright-puppeteer):
  the integration flow with working examples — find the sitekey, request a token, inject it, submit.
- [reCAPTCHA v2, v3 and Enterprise: what actually differs](https://kagedcap.io/guides/recaptcha-v2-v3-enterprise-differences):
  what a v3 score is and is not, what `action` binds, and which task name handles each.
- [Do you need a proxy to solve reCAPTCHA?](https://kagedcap.io/guides/do-you-need-a-proxy-to-solve-recaptcha):
  ProxyLess versus proxied, why the minting IP matters, and the failure modes.

## Docs

- [Documentation](https://kagedcap.io/docs): full API reference — task types, request and
  response shapes, error codes, proxy rules, and the v2 async job endpoints.
- [Pricing](https://kagedcap.io/#pricing): live per-1,000-solve pricing by SKU.
- [Status](https://kagedcap.io/status): current fleet health.

## Optional

- [Changelog](https://kagedcap.io/changelog): product and API changes.
- [Terms](https://kagedcap.io/terms): terms of service, acceptable use and privacy.
- [Partners](https://kagedcap.io/partners): referral programme.