Search Service
browser: off stream: idle no blocks

Access

API keys

A key reaches /api/search, /api/fetch and /api/engines, sent as Authorization: Bearer <key> or X-Api-Key. Only its hash is stored, so it is shown once, right after it is created.

Admins

Your account

Changing the password signs you out on every other device.

Search

GET /api/search?q=…

Response

No search yet.

CAPTCHA

Outcome

No run yet.

Detect and Solve work on the tab opened here, or on the tab you are watching in the viewer. Solving takes as long as the solver's budget allows, so the buttons stay disabled until it is done. The reCAPTCHA demo serves a dynamic grid (“click verify once there are none left”) only now and then — reload the challenge in the viewer to get one.

Browser

Profiles

Searches rotate over the profiles below, one query per profile at a time. Warm up a fresh profile by hand — open it, use Google normally for a few minutes, then finish — a profile with real history is challenged far less. The pool is saved to profiles.json next to the profile directories.

No open tabs. Run a search or open a URL.

Every open tab of every profile, refreshed a couple of times a second. Click one to take it over — mouse, wheel and keyboard are replayed into the page, which is how a CAPTCHA the service could not pass gets finished.