Anti-Captcha API

Name: Anti-Captcha API API
Brand: Anti-Captcha API
Availability: InStock

★ Only Publicly Available SpecData EnrichmentData TransformationapiKey7 EndpointsREST

For Agents

Submit CAPTCHA-solving tasks (image, reCAPTCHA, hCaptcha, FunCaptcha) to Anti-Captcha and poll for solutions. Suited to scraping or testing agents that need to clear human-verification steps.

Quickstart

Get started with Anti-Captcha API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"solve a reCAPTCHA challenge"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Anti-Captcha API API.

Submit a CAPTCHA-solving task for image, reCAPTCHA, hCaptcha, FunCaptcha, or GeeTest variants

Poll the task result endpoint to retrieve the solver's response token or text

Read the current account balance to gate task submission against budget

Inspect queue statistics to estimate solving latency before submitting a task

GET STARTED

Start building with Anti-Captcha API API

Explore with Jentic

View OpenAPI Spec

Jentic publishes the only available OpenAPI specification for Anti-Captcha API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Anti-Captcha API, keeping it validated and agent-ready. Anti-Captcha is a paid CAPTCHA-solving service that exposes seven endpoints for submitting solving tasks (image, reCAPTCHA, hCaptcha, FunCaptcha and friends), polling for the human-or-worker-produced solution, checking account balance, and reading queue statistics. Each task is created with POST /createTask, then polled via POST /getTaskResult until the solution is returned. Authentication uses the clientKey query parameter on every request.

Use Cases

Patterns agents use Anti-Captcha API API for, with concrete tasks.

★ Scraping Pipeline Unblock

Resolve CAPTCHA prompts that interrupt a scraping run by calling POST /createTask with the page's site key and target URL, then polling POST /getTaskResult until the solution token is returned. The token is injected back into the form submission and the scrape continues. Works for reCAPTCHA v2/v3, hCaptcha, FunCaptcha, and image CAPTCHAs without the agent needing to render the challenge.

Call POST /createTask with the site key and page URL, then poll POST /getTaskResult every 5 seconds until status is 'ready' and parse the gRecaptchaResponse

Pre-Run Budget Guard

Before launching a long-running automated job that will hit many CAPTCHAs, check the account balance via POST /getBalance and inspect queue depth via POST /getQueueStats so the agent can decide whether to proceed, top up, or wait. This avoids burning compute on a job that will stall halfway through with insufficient funds.

Call POST /getBalance; if under a configured threshold, halt the run and emit a top-up alert instead of submitting tasks

AI Agent Form Automation via Jentic

An AI agent automating a multi-step web form (e.g., signup or test-account creation) can use Anti-Captcha through Jentic to clear CAPTCHA gates without managing the clientKey directly. Jentic's intent search routes the agent to POST /createTask with the right task-type schema, and the clientKey is loaded from the vault at execution time so it never enters the agent's tool context.

Search Jentic for 'solve a reCAPTCHA challenge', load POST /createTask with task type RecaptchaV2TaskProxyless, and execute with the page's site key and URL

Key Endpoints

7 endpoints — jentic publishes the only available openapi specification for anti-captcha api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/createTask

Submit a CAPTCHA-solving task

POST

/getTaskResult

Poll a task's result by task ID

POST

/getBalance

Return the account's current balance

POST

/getQueueStats

Return queue length and worker stats per task type

POST

/sendFunds

Transfer funds between Anti-Captcha sub-accounts

POST

/getAppStats

Return app-level statistics for a software ID

POST

/test

Test connectivity to the Anti-Captcha endpoint

POST

/createTask

Submit a CAPTCHA-solving task

POST

/getTaskResult

Poll a task's result by task ID

POST

/getBalance

Return the account's current balance

POST

/getQueueStats

Return queue length and worker stats per task type

POST

/sendFunds

Transfer funds between Anti-Captcha sub-accounts

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Anti-Captcha clientKey values are stored encrypted in the Jentic vault. Agents receive scoped execution access only — the clientKey never enters the agent's prompt or tool context, which matters because the key bills directly against the Anti-Captcha balance per solved task.

Intent-based discovery

Agents search by intent (e.g., 'solve a reCAPTCHA challenge') and Jentic returns POST /createTask with the right task-type schema, so the agent does not need to memorise task-type names like RecaptchaV2TaskProxyless from the docs.

Time to first call

Direct Anti-Captcha integration: 0.5-1 day to wire the create-then-poll flow, error handling, and balance checks. Through Jentic: under 30 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

2Captcha API

2Captcha is a near-identical CAPTCHA-solving service with the same submit/poll flow.

Choose 2Captcha when the agent already has a 2Captcha balance or needs a different solver pool for redundancy.

Complementary

Fingerprint API

Fingerprint identifies devices before a CAPTCHA gate is reached, reducing how often a solver is needed.

Choose Fingerprint on the defending side when the agent operates a site that wants fewer CAPTCHA prompts; pair with Anti-Captcha on the requesting side.

Complementary

Onfido API

Onfido handles human identity verification, a separate concern from automated CAPTCHA solving.

Choose Onfido when the agent needs to verify a real human user's identity rather than clear a bot-detection challenge.

FAQs

Specific to using Anti-Captcha API API through Jentic.

Why is there no official OpenAPI spec for Anti-Captcha API?

Anti-Captcha publishes its API documentation at anti-captcha.com/apidoc as HTML reference rather than a downloadable OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Anti-Captcha via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Anti-Captcha API use?

Anti-Captcha uses an API key called clientKey that is sent as a query parameter on every request. Through Jentic the clientKey is stored in the encrypted vault and injected at execution time, so the raw key never enters the agent's prompt context.

Can I solve reCAPTCHA v2 with the Anti-Captcha API?

Yes. POST /createTask with task type RecaptchaV2TaskProxyless and the target page's website URL and site key, then poll POST /getTaskResult until status becomes 'ready' and read the gRecaptchaResponse field for the token to inject into the form.

What are the rate limits for the Anti-Captcha API?

The OpenAPI spec does not declare explicit rate limits, but Anti-Captcha throttles by available worker pool — submitting more tasks than the queue can absorb increases solving latency rather than returning 429. Use POST /getQueueStats to size your concurrency to the live queue depth.

How do I check my Anti-Captcha balance through Jentic?

Run pip install jentic, then search Jentic for 'check Anti-Captcha balance'. Jentic returns POST /getBalance with the request schema. Execute with no body parameters; the clientKey is injected from the vault.

How do I poll for a CAPTCHA solution after creating a task?

After POST /createTask returns a taskId, poll POST /getTaskResult with that taskId every few seconds. The response status is 'processing' until the solver completes, at which point status becomes 'ready' and the solution field contains the token or text.