The desk
Open a desk and you get 100 trial credits, a private address at mail.captell.run, and an API key. Add a bot by name. That bot gets its own address and its own key. Solves from the bot spend the desk balance. whoami, get_balance, and GET /api/v1/balance all report that same balance.
The dashboard has a note for each kind of bot. Copy that note. It already contains the address and the key, and it only tells the bot where to send the captcha. You do not sit in the loop.
Credits
One credit is one tenth of a cent. An image letter is 4 credits. A reCAPTCHA v2, v3, Turnstile, or hCaptcha token is 10. The price list has the rest. Packs add credits in advance. Card checkout is not connected, so the buttons on the desk add trial credits and do not charge a card.
A failed solve puts the credits back. A request the desk refuses, such as a screenshot of a checkbox or a picture under 100 bytes, uses nothing.
Three doors
Use the door the bot can actually finish. The wrong door is how the person ends up babysitting again.
- Mail, for a picture of letters or numbers. The reply is short text the bot types.
- The page helper, for a widget in a browser the bot can click. The CAPTELL Page Helper extension reads the site key and places the token. A userscript is the fallback.
- MCP or HTTPS, for a bot or script that can call a public tool and place the answer itself.
Mail a picture
For letters and numbers only. Attach one png, jpg, webp, or gif of only the code. The file must be at least 100 bytes. Crop so the code fills the frame. Do not paste a link. Do not describe the letters in the body. Put token and reply in every letter. The answer is mailed to the reply address.
To: your-bot@mail.captell.run Subject: ImageToText token: ct_live_your_key reply: bot@example.com Attach one image file of only the code. png, jpg, webp, or gif. At least 100 bytes. Crop so the code fills the frame.
The reply looks like this. The bot types the answer line into the form.
status: ready
type: ImageToText
credits: 4
balance: 96
answer: R4K9
{
"solution": { "text": "R4K9" }
}Page helper
For Google, Cloudflare, and hCaptcha. The helper is the CAPTELL Page Helper, CAPTELL’s own Chrome and Edge extension, version 2026.10.4.16. The person loads it once per browser from https://captell.run/extension. The bot opens that bot’s connect link, https://captell.run/extension/connect?token=…, in the browser that shows the page, and the page says Connected. The popup shows the version and the masked key. One key per browser, because each bot has its own browser. Fallback: a browser that cannot load an extension opens https://captell.run/captell.user.js?token=… with that bot’s own key. The page helper is the CAPTELL Page Helper extension, version 2026.10.4.16. Its popup shows the version and this bot's masked key. If that browser runs the captell.user.js fallback instead and Tampermonkey offers 2026.10.4.16, accept it. A cookie wall must be accepted before the captcha and the Place the check button appear. A click anywhere inside the button rectangle counts. If the register page is already signed in as another account, log out and reopen it as a guest. Do not cancel that other registration. If the form is visible, the cookie wall is gone, a captcha label is on the page, and Place the check never appears, stop that board and report the URL and the label text.
One corner button, named Place the check. A cookie wall must be accepted before the captcha and the Place the check button appear. A click anywhere inside the button rectangle counts. A click always changes the button to Placing…, No widget, Missing site key, or Unsupported type. If the button says Missing site key, stop. Do not retry four times. Reloading will not invent a key. If the button says Unsupported type, stop. Do not retry. FunCaptcha, GeeTest, and KeyCaptcha are unsupported. A Security Check label with no checkbox is still a captcha. Click Place the check first. Do not submit only because no human box is visible. If no captcha is visible, and there is no Security Check label, click the site's submit button. If a captcha then appears, use Place the check. Submit only when the button says exactly "Placed. Submit the form." and the site's own human box is checked, or there is no empty checkbox and no open image grid. Placing… ends as Placed, No token, a short solver error, or it returns to Place the check after 3 minutes. Do not click while it says Placing…. If the button says No token, or a short solver error, do not submit. Click Place the check again, up to 4 tries. A failed try is not charged. Placed clears when the token expires, in about two minutes. Submit soon after Placed. Do not submit an old token. If the page says "You did not pass the security check. Please try again." or "Captcha Prüfung fehlgeschlagen!", click Place the check. If the button is missing, reload once. Do not submit again until the button says Placed again. If the page says "Die Registrierung ist wegen Spamschutzmaßnahmen fehlgeschlagen." or "No soup for you!" or "Your registration has been rejected as it resembles spam-like or automated behavior. Please contact the administrator for further information or assistance." after a real Placed submit, try once more: click Place the check, and submit as soon as it says Placed. If the board says it again, that is the board's spam filter. Stop that board. Do not click Place the check again for it. If an image grid is open, including "Please click on the icon that is different.", do not click the pictures and do not submit. Wait for Placing… to finish. If the grid stays open after the button settles, click Place the check again. It counts as one of the four tries. If the register page is already signed in as another account, log out and reopen it as a guest. Do not cancel that other registration. If the form is visible, the cookie wall is gone, a captcha label is on the page, and Place the check never appears, stop that board and report the URL and the label text. Click Place the check. It fills a math answer or a question such as "Wie heißt die Hauptstadt von Deutschland?" and places the captcha if there is one. Submit only when the button says exactly "Placed. Submit the form." If the button says "Could not answer", stop and report the question text. An unknown page state can come back as one instruction that stays on this registration form. Do not type the token. Do not send a screenshot. Do not mail the page.
The CAPTELL Page Helper 2026.10.4.16 is loaded once in the browser that shows the page: https://captell.run/extension Open https://captell.run/extension/connect?token=ct_live_your_key in that browser. The page says Connected when the helper holds this bot's key. If that browser cannot load an extension, open https://captell.run/captell.user.js?token=ct_live_your_key instead. One install per browser, using this bot's own key, because each bot has its own browser. A picture of letters, including a phpBB Bestätigungscode, is one tight crop of only the code, at least 100 bytes. Subject: ImageToText. Do not click Place the check for it. A page whose only captcha is that picture has no Place the check button. If the reply says it was not read, crop closer and send that new file the same way. Google, Cloudflare, or hCaptcha: Do not open https://captell.run/login. Do not use hcaptcha.com. The page helper is the CAPTELL Page Helper extension, version 2026.10.4.16. Its popup shows the version and this bot's masked key. If that browser runs the captell.user.js fallback instead and Tampermonkey offers 2026.10.4.16, accept it. A cookie wall must be accepted before the captcha and the Place the check button appear. One corner button, named Place the check. A click anywhere inside the button rectangle counts. A click always changes the button to Placing…, No widget, Missing site key, or Unsupported type. A click that stays on Place the check did not run. Click again. That click does not count toward the four tries. If the button says Missing site key, stop. Do not retry four times. Reloading will not invent a key. If the button says Unsupported type, stop. Do not retry. FunCaptcha, GeeTest, and KeyCaptcha are unsupported. A Security Check label with no checkbox is still a captcha. Click Place the check first. Do not submit only because no human box is visible. If no captcha is visible, and there is no Security Check label, click the site's submit button, unless the form asks a math or knowledge question. Then click Place the check. If a captcha then appears, use Place the check. Submit only when the button says exactly "Placed. Submit the form." and the site's own human box is checked, or there is no empty checkbox and no open image grid. Placing… ends as Placed, No token, a short solver error, or it returns to Place the check after 3 minutes. Do not click while it says Placing…. If the button says No token, or a short solver error, do not submit. Click Place the check again, up to 4 tries. A failed try is not charged. Placed clears when the token expires, in about two minutes. Submit soon after Placed. Do not submit an old token. If the page says "You did not pass the security check. Please try again." or "Captcha Prüfung fehlgeschlagen!", click Place the check. If the button is missing, reload once. Do not submit again until the button says Placed again. If the page says "Die Registrierung ist wegen Spamschutzmaßnahmen fehlgeschlagen." or "No soup for you!" or "Your registration has been rejected as it resembles spam-like or automated behavior. Please contact the administrator for further information or assistance." after a real Placed submit, try once more: click Place the check, and submit as soon as it says Placed. If the board says it again, that is the board's spam filter. Stop that board. Do not click Place the check again for it. A badge-only check can say Placed when the token is in the form and there is no empty checkbox and no open image grid. If an image grid is open, including "Please click on the icon that is different.", do not click the pictures and do not submit. Wait for Placing… to finish. If the grid stays open after the button settles, click Place the check again. It counts as one of the four tries. If the register page is already signed in as another account, log out and reopen it as a guest. Do not cancel that other registration. If the form is visible, the cookie wall is gone, a captcha label is on the page, and Place the check never appears, stop that board and report the URL and the label text. Click Place the check. It fills a math answer or a question such as "Wie heißt die Hauptstadt von Deutschland?" and places the captcha if there is one. Submit only when the button says exactly "Placed. Submit the form." If the button says "Could not answer", stop and report the question text. An unknown page state can come back as one instruction that stays on this registration form. Username already used, a banned email, "Entering a password is required.", and "Die Eingabe eines Passworts ist erforderlich." are form errors. Do not click Place the check again for them. Do not send a screenshot. Do not type the token. Do not mail the page.
MCP
Hermes, Claude, Cursor, and any bot that can add a public tool. Point the client at https://captell.run/api/mcp with the seat’s key. The tools are solve_captcha, get_balance, whoami, and get_task. solve_captcha returns status, credits, balance, and the answer. A job is also GET https://captell.run/api/v1/tasks/:id.
{
"mcpServers": {
"captell": {
"url": "https://captell.run/api/mcp",
"headers": { "Authorization": "Bearer ct_live_your_key" }
}
}
}Hermes uses the same values under mcp_servers in ~/.hermes/config.yaml. The pages for each bot have the exact note.
HTTPS
POST JSON to https://captell.run/api/v1/solve. Send Authorization: Bearer with the key. A token field in the JSON is also accepted. The response field to read is answer. Place a widget token within about two minutes and call the page callback. Balance is GET https://captell.run/api/v1/balance. POST JSON to https://captell.run/api/v1/answer with the same Authorization Bearer and a question field, or pageText when the page state is not a known button label. The response field is answer, or one instruction that stays on the registration form. If it cannot answer, the message is Could not answer.
curl -X POST https://captell.run/api/v1/solve \
-H "Authorization: Bearer ct_live_your_key" \
-H "content-type: application/json" \
-d '{"type":"RecaptchaV2","websiteURL":"https://the-page.example","websiteKey":"the-site-key"}'Every type
ImageToText needs body, raw base64, no data: prefix. Page checks need websiteURL and websiteKey. FunCaptcha uses websitePublicKey. GeeTest uses gt. Worked bodies for each type are on the samples page.
| Type | Credits | Needs |
|---|---|---|
| ImageToText | 4 | body |
| RecaptchaV2 | 10 | websiteURL, websiteKey |
| RecaptchaV3 | 10 | websiteURL, websiteKey |
| RecaptchaV2Enterprise | 25 | websiteURL, websiteKey |
| Turnstile | 10 | websiteURL, websiteKey |
| HCaptcha | 10 | websiteURL, websiteKey |
| GeeTest | 9 | websiteURL, gt |
| FunCaptcha | 15 | websiteURL, websitePublicKey |
When it refuses
- A picture under 100 bytes. No credits.
- Do not send a screenshot. A page check needs the page address and the site key. No credits.
- A missing field for that type. The message names the field. No credits.
- An unknown key. Nothing is solved.
- A paused seat. The letter is refused and the balance stays put.
- Not enough credits. The job does not run. Add a pack on the desk.
- The picture was not read. Crop closer and send that new file the same way. The credits come back.
Until an Anti-Captcha key is set on the server, answers are labeled sandbox and are not live tokens.
Which bot uses which door
| Who | Door | What they stop doing |
|---|---|---|
| Humans | The desk | They stop being called every time a check appears. They still hold the credits and can pause a bot. |
| Agents | Whichever they can finish | They stop holding the run until a person notices. |
| Grok | Mail, and the page helper | Letters are mailed and typed. Widgets use Place the check in the browser that shows the page. |
| Hermes | MCP | One block in ~/.hermes/config.yaml. Pictures and tokens both come back in the call. |
| Claude | MCP | Merge the JSON in Claude Desktop, then tell the chat to use the server. |
| Cursor | MCP | Add the JSON under MCP settings, and a rule so the agent does not stop and ask. |
| ChatGPT | Only when that chat can send a letter and read the reply. A plain chat box cannot. | |
| Scripts | HTTPS | The script reads answer and places it. A person is not a step in the loop. |