feat: Robotex landing — access by API key, Turnstile passes

- badge and limits: requests need an X-API-Key, the demo instance test key
  is in the Redmine wiki; the example request sends the header
- drop the "early MVP" and "Turnstile is unstable" caveats

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
protokeyandClaude Opus 5.5 committed 2026-10-13 21:33:58 +04:00
1 parent f7d0f27faa
commit 632b959a06
2 files changed
+10 -10

No files matched your search

+5 -5
View File
@@ -3,7 +3,7 @@ title: "Robotex"
tagline: "A browser for your bots, over an API"
description: "Robotex gets past anti-bot protection, runs a scenario on the page and hands your bot the cookies. From there the bot works with plain HTTP requests."
domain: "https://robotex.sokolab.xyz/"
badge: "Free · open access"
badge: "Free · demo key in the wiki"
post: "/blog/robotex-browser-automation-api"
postLabel: "How Robotex works"
build:
@@ -36,7 +36,7 @@ features:
- title: "Scenarios"
text: "More than opening a page. Fill a form, click, move the mouse, wait for an element, grab a piece of HTML or text."
- title: "Anti-bot pages"
text: "Detects a Cloudflare check before and during a scenario and gets through it. If it escalates to an image captcha, sends it to a recognition service."
text: "Detects a Cloudflare check before and during a scenario and gets through it, Turnstile included. If it escalates to an image captcha, sends it to a recognition service."
- title: "Captcha"
text: "The `captcha` step solves hCaptcha and other captchas via 2captcha before the form is submitted."
- title: "Profiles"
@@ -49,7 +49,7 @@ features:
how:
title: "How it works"
steps:
- "The bot sends a URL, an action scenario and its proxy to `POST /v2/tasks`. The task is queued, and the response carries a link to the result and a `session_id` cookie."
- "The bot sends its API key, a URL, an action scenario and its proxy to `POST /v2/tasks`. The task is queued, and the response carries a link to the result and a `session_id` cookie."
- "A free worker opens the page in Chrome, passes the checks and runs the scenario. The bot polls the link until the task is `done`."
- "The bot gets the cookies and User-Agent and keeps browsing on its own, **with the same UA and through the same proxy**."
- "When it needs a browser again, it sends `session_id`. If it asked to keep the window (`browser_idle_timeout`), the task runs there, even without a `url`. If not, Chrome starts with the same profile."
@@ -58,6 +58,7 @@ how:
- caption: "Task"
body: |
POST https://app.robotex.sokolab.xyz/v2/tasks
X-API-Key: <key>
{
"url": "https://example.com/login",
@@ -110,12 +111,11 @@ engine:
limits:
title: "Where it stands, honestly"
items:
- "**It's an early MVP.** Access is open, no sign-up or keys, but the API may change."
- "**Access by API key.** A test key for the demo instance is in the [project wiki](https://redmine.sokolab.xyz/projects/robotex/wiki), send it in the `X-API-Key` header."
- "An open window takes up a browser slot. Don't keep it longer than you need."
- "For now all workers run on a single server."
- "**It's free.** You only pay for your own proxies and, if needed, 2captcha."
- "Proxy quality matters a lot: no fingerprint will help on a dirty IP."
- "Turnstile doesn't pass on every site yet, I'm working on stability."
community:
title: "Community"