# Compatibility APIs

Compatibility routes share your Ninetile account, balance, limits and API key. They support hCaptcha, not every task offered by the original services. Review the native API reference for billing and task behavior.

- 2Captcha-style: `https://api.ninetile.io/compat/2captcha` using `in.php` and `res.php`.
- CapSolver-style: `https://api.ninetile.io/compat/capsolver` using `createTask`, `getTaskResult` and `getBalance`. Equivalent route prefixes include `/compat/anticaptcha` and `/compat/capmonster`.
- NopeCHA-style token API: `https://api.ninetile.io/compat/nopecha`.

Pass your Ninetile `nt_live_` key where the compatible client expects a key. Use the native endpoints for the complete Ninetile-specific response, feedback and usage capabilities. Unsupported task types or options are not guaranteed to work.

## Supported createTask task types

The createTask adapter accepts `HCaptchaTask`, `HCaptchaTaskProxyless`, `HCaptchaEnterpriseTask`, `HCaptchaEnterpriseTaskProxyless`, `HCaptchaTurboTask` and `HCaptchaTurboTaskProxyless`. Proxyless tasks use the service pool; non-proxyless tasks require proxy fields or a proxy string. Set `websiteKey` and `websiteURL`; enterprise data may be passed as `enterprisePayload.rqdata`.

Send `clientKey` and `task` to createTask; then send `clientKey` and `taskId` to getTaskResult. Processing responses use `status: processing`; ready responses contain `solution.token`, `solution.gRecaptchaResponse`, and `solution.userAgent`. These dialects use their own error envelopes. The solver does not return a `resp_key`.

Canonical: https://ninetile.io/docs/compatibility