New task types, API changes, and anything that affects an integration you have already written. Entries marked breaking need you to do something; the rest do not.
POST /v1/getResult, /v1/createTask and /v1/checkTask are live. A request is authenticated by API key, checked against the types your account is enabled for, admitted against your thread limit and your balance, and only then sent to a solver. Successful solves are charged at the published per-1000 price; every failure settles at zero.
hCaptcha and hCaptcha Enterprise are wired and enabled on new accounts by default. Both take a URL and a site key and return a token.
All three were listed as accepting traffic and were not — calls to them would have been refused. They are now shown as planned, which is what they are. The task fields published for each are settled, so an integration written against them today will work unchanged on release.
Per-type success rates and medians, and the headline figures on the home page, were placeholders written by hand before the service could measure anything. They have been removed rather than restated. Every figure on the site is now derived from real solves, and prints a dash where there are not enough of them. The new /status page shows what is measured, per type, along with how many solves each figure rests on.
voidcaptcha.com/status carries per-type success rates and medians over the last 30 days, plus whether each solver is currently reachable. It deliberately publishes no uptime percentage until an external prober exists to measure one honestly.
Starting from today. Everything before this line was built without one, and rather than reconstruct dates after the fact the record simply begins here.