Click when green
Reaction-time (click when ready)
Difficulty is a cost dial, not a security dial — harder = more work, never a better bot/human test. The detector convicts at every level.
The challenge auto-serves on load · ↻ new challenge
Pass the gate on the left. Kitsune’s coherence engine scores your client from the edge at the same time — because solving a gate is a cost or Turing test, not proof you’re human.
Gate verdict
did you solve the puzzle?
Detector verdict
does your client hold together?
Endpoints — point your own solver here
The gate is just an HTTP protocol on Kitsune’s owned arena service (allow-list-scoped — it only ever talks to itself). Script a bypass against:
- GET
/arena/reaction - POST
/arena/reaction/verify
Wait for the box to turn green, then click it as fast as you can. A reaction latency below the human physiological floor (~150ms), or a click that reaches the server before the go (anticipation), convicts — a bot reacts faster than any human hand-eye loop. Server-observed, unforgeable in the too-fast direction. A self-hosted reproduction of the documented mechanism — never a third-party widget. The detector reads the same coherence engine that scores the home page.
How this works & the ethics
The gate is a self-hosted service Kitsune runs (the owned arena service). It reproduces the
documented, open mechanism above — it never contacts, proxies to, or solves a third-party
challenge (Cloudflare Turnstile, reCAPTCHA, hCaptcha). The reference solvers only ever talk to our own gates. The detector
verdict comes from the same coherence engine that scores the home page, reading your client over the edge.