Skip to content
easycaptcha.to

Task comparison

Regular vs enterprise hCaptcha token tasks

Compare request data, permission requirements, billing, and evaluation cohorts for easycaptcha regular and enterprise token jobs.

By the easycaptcha team · Published

Comparison table for Regular vs enterprise hCaptcha token tasks, covering Type, Public integration data, Enterprise data, Access.
The comparison criteria shown here are explained in the article; this is not a performance benchmark.View full-size illustration

A regular token request and an enterprise token request have different easycaptcha task types. Enterprise work requires account approval and the integration’s rqdata. Supplying an enterprise-looking sitekey does not replace that permission or add missing request data.

Eligibility and configuration

The same account can therefore encounter two distinct failures: the operation may not be permitted, or its challenge configuration may be wrong. Preserve the error distinction so retries do not hide a setup issue.

Compare the request contract

Field or requirement Regular task Enterprise task
Type hcaptcha_token hcaptcha_enterprise_token
Public integration data Sitekey and URL Sitekey and URL
Enterprise data Not the enterprise contract rqdata required
Access Standard paid task eligibility Approved enterprise access
Price Regular token rate Enterprise token rate

See the API reference for precise validation and enterprise setup for access requests. Proxy and mode options still need to follow the documented request schema.

Use the same lifecycle with distinct inputs

Both create accepted work that can first be queued or running. Persist the task ID and retrieve it until completion or failure. A local timeout does not convert the operation to regular work or cancel it.

Do not switch types automatically after a failure. That changes the requested operation, potentially adds paid work, and can invalidate the comparison. Diagnose permission, input, network, and terminal task errors before deciding to create anything new.

Evaluate each configuration honestly

A successful regular-token demonstration does not establish enterprise acceptance. Use separate cohorts with the actual required data, and record the intended application outcome. Compute cost using the relevant rate and selected mode.

Challenge cohort design explains how a mixed workload can distort an aggregate success rate. The sitekey guide helps separate public configuration, customer credentials, and site-owner secrets.

Frequently asked questions

Can any easycaptcha account submit enterprise token jobs?

Enterprise token work requires explicit account access. Request configuration does not substitute for that entitlement.

How do enterprise token inputs differ from regular token inputs?

Both require sitekey and page URL. The enterprise task also requires rqdata under its documented request contract.

How do I start using the easycaptcha API?

Create an account and get an API key, then follow the getting-started guide. Submit recognition or token tasks through raw HTTP or the typed Python and JavaScript SDKs.

Try easycaptcha

Build with the easycaptcha API

Review easycaptcha's regular and enterprise task requirements before setting up your token integration.

Submit hCaptcha recognition or token jobs, retrieve results, and send feedback through one API. Typed Python and JavaScript SDKs help you get started.