Try solvethree with the welcome credit
Use the $5 welcome credit for a 5–10-solve trial against the target you actually need. Check whether the target accepts the result before paying for more credit.
On this page
What the $5 welcome credit covers
The welcome credit is $5. The minimum paid deposit is $10; that’s a separate amount, not the size of the trial credit. Budget for your own proxy costs separately.
| Product | Price per 1,000 solves | Whole ready tasks covered |
|---|---|---|
| reCAPTCHA Enterprise | $2.00 | 2,500 |
| Kasada | $1.25 | 4,000 |
| TMPT | $0.99 | 5,050 |
These are generated solutions, not guaranteed successful requests to the target. A ready task is billed; a failed solve is refunded. A target rejecting a ready solution does not automatically refund the solve.
Check that your target is ready for a trial
- reCAPTCHA Enterprise: Set up the target site in the console and confirm that an active profile is available to your workspace. Sending a hostname and action does not create a profile. Create the profile before starting the trial.
- Kasada: Standalone solving currently supports HTTPS targets on
www.ticketmaster.com, not arbitrary Kasada-protected sites. Use the target URL; the solution is a headers object. - TMPT: Use the exact event URL with action
Event, or the sign-in entry URL with actionLogin. The returned token is the rawtmptcookie value, not a reCAPTCHA token.
Each task needs a proxy input. For request details, use the first-solve instructions, Kasada contract, or TMPT contract rather than adapting one product’s fields to another.
Run 5–10 solves and inspect the actual result
- 1.
Start with one complete request
Create a task and follow it to a terminal status. Keep its task ID. If you use a requestId and creation times out, recover the existing task by resubmitting the same request with that ID instead of creating duplicate work.
- 2.
Submit the right solution to the target
Only
readycontains a usable solution. Submit the Enterprise token, apply the Kasada headers together, or use the TMPT cookie as appropriate. Use the returneduserAgentandsecChUaidentity with the successful proxy; don’t switch to an unrelated browser identity or IP. - 3.
Record what happened at both ends
For each attempt, keep the task ID, terminal status, billed cost, and the target’s actual response. For failed tasks, record
errorCodeanderrorand stop polling. Keep API keys, proxy credentials, tokens, and cookies out of logs. - 4.
Fix an obvious mismatch before continuing
If a ready solution is rejected, inspect the outgoing target request first: did it contain the returned solution, browser identity, and correct proxy? If task creation or solving failed, inspect that error separately. Don’t assume every failure means the credit ran out.
Once the first request is correctly wired, continue to 5–10 solves. Compare the number of ready tasks with the number the target actually accepted, alongside solve charges and proxy costs. That small sample can expose integration problems; it isn’t a reliable acceptance-rate guarantee.
Ten ready tasks cost $0.02 for Enterprise, $0.0125 for Kasada, or $0.0099 for TMPT, before proxy costs. If the target accepts the results and the cost works for your use case, the next paid deposit starts at $10.
Sources and API reference
Run your first task.
Start with $5 in workspace credit.