Can you use solvethree without supplying a proxy?

For reCAPTCHA Enterprise, send a hostname, an action and exactly one proxy input to POST /v1/tasks. Authenticate with a workspace API key using Bearer authorization, keeping the key on your server. The target site must already have an active profile available to your workspace; the request itself doesn't create one.

{
  "site": "accounts.example.com",
  "action": "login",
  "proxy": "http://user:[email protected]:8080",
  "requestId": "example_login_001"
}

Replace the example hostname, action and proxy URL with your target's values and your proxy credentials. recaptchaType defaults to enterprise-v3, so it isn't needed here. Don't add a type or url field.

requestId is optional, not another required input. If task creation times out, resending the same request with the same ID recovers the existing task rather than creating another one. Don't reuse that ID for different inputs.

Instead of proxy, you can supply proxyCandidates with up to six distinct HTTP or HTTPS proxy URLs. Those URLs must have no path, query or fragment. Candidates let solvethree try alternative egress; they don't remove the need to supply proxies or guarantee that one will work.

Configuring a proxy in your HTTP client routes your API connection through that proxy. It doesn't replace the proxy or proxyCandidates input in the task body. These settings control different connections: your request to solvethree, and the proxy used for solving.

You also need to plan the later request to the target. Submit the solution using the successful proxy and the returned userAgent and secChUa browser identity. If your proxy vendor rotates exits, use its session or pinning feature so solving and submission can share an exit.

Only a ready task contains a usable solution. That means the solution was generated, not that your application request succeeded. A working proxy connection—or a vendor's residential, mobile or datacenter label—doesn't establish a CAPTCHA score.

These are different integration models, not interchangeable request formats. Check the exact supported task type and submission requirements in each provider's documentation, including CapSolver's reCAPTCHA v3 documentation. Don't carry solvethree's browser-identity or proxy requirements over to another provider without checking its contract.

• For solvethree, combine the solve price with your proxy supplier's charges. Include any access, traffic or session features your chosen plan bills for.
• For a provider-proxyless offering, compare its task price and confirm that included proxies apply to the exact Enterprise task you need.
• Include the integration work: solvethree requires site-profile setup, proxy configuration and matching the successful proxy and returned identity during submission. Compare that with the other provider's documented requirements.

Failed solvethree solves are refunded. Check proxy billing separately rather than treating that refund as covering third-party usage.

If you can't supply a proxy, the current solvethree API doesn't fit that requirement. If you can, compare services using your actual solve-and-submit workflow—not proxy labels or the solve price alone.