FunCaptcha, now branded Arkose Labs, is the type that asks for something a simple image model cannot answer: rotate an object to a pose, pick the matching pair, follow a path. It is common on large consumer platforms precisely because it is hard to automate. We support it, including the matching variant, through a single endpoint.
Arkose does not only look at the answer; it looks at the session that produced it. A challenge solved with no browser context at all is more likely to be escalated or refused. When a solve succeeds but the site still rejects it, adding the same proxy and user agent that the rest of your flow uses is the first thing to try.
Send the public key and URL to the token endpoint, then poll for the result. Error 14 while polling means the job is still working, which is normal for FunCaptcha because the challenges are heavier than an image read. Once the token arrives, write it into the token field the page expects and submit.
One credit per accepted solve, with polling free and refused submissions uncharged. Given the complexity of the challenge this sits well below a token for reCAPTCHA, which costs twenty. New accounts start with 200 free solves.
curl -X POST https://fuckcaptcha.top/v1/token/funcaptcha \\
-H "Authorization: Basic $NSK_KEY" \\
-d '{"sitekey":"<sitekey>","url":"<page url>"}'Charged per solve: one credit for each recognition request, and polling for the result is free. Signing up includes 200 free solves.
Match is the pairing variant where two panels have to be matched up. It is a distinct type on the endpoint, so choose it from the challenge you actually see rather than assuming the default.
When you have them, yes. Arkose weighs session signals, so cookies, user agent and proxy that match the surrounding traffic make a token far more likely to be accepted on the first attempt.
The challenges are three dimensional and interactive, so the upstream needs more time. Error 14 during polling is expected rather than a problem.
These run the same underlying challenge with extra site configuration. Where a site has tightened its own validation, a valid token can still be refused, which is a site policy decision rather than a recognition failure.
A submission the upstream refuses is not charged. Once a job is accepted it costs one credit, so a retry should use a fresh challenge.