OpenClaw
Give an autonomous browser agent captcha-solving via MCP or the raw API.
Loading…
Give an autonomous browser agent captcha-solving via MCP or the raw API.
Loading…
OpenClaw is an autonomous, browser-driving agent. Like any agent that can call external tools or HTTP APIs, it can clear captchas with NoCaptchaAI in one of two ways: through the MCP server if your build supports MCP, or by calling the API endpoints directly.
If your OpenClaw version speaks MCP, register the NoCaptchaAI MCP server
with the standard mcpServers config wherever OpenClaw reads its tool configuration:
{
"mcpServers": {
"nocaptchaai": {
"command": "npx",
"args": ["-y", "nocaptchaai-mcp"],
"env": {
"NOCAPTCHAAI_API_KEY": "your_key"
}
}
}
}
The agent then has a solve_captcha tool and can call it whenever it hits a challenge.
If MCP isn't available, instruct the agent to call the endpoints itself. The flow is:
POST /createTask to submit the challenge, then poll POST /getTaskResult until
status is ready:
# 1. Create the task
curl -s https://api.nocaptchaai.com/createTask \
-H "Content-Type: application/json" \
-d '{
"clientKey": "your_key",
"task": {
"type": "AntiTurnstileTask",
"websiteURL": "https://example.com",
"websiteKey": "0x4AAAAAAA..."
}
}'
# -> { "taskId": "..." }
# 2. Poll until status is "ready"; the token is in "solution"
curl -s https://api.nocaptchaai.com/getTaskResult \
-H "Content-Type: application/json" \
-d '{ "clientKey": "your_key", "taskId": "..." }'
Get your_key from the dashboard.
Setup depends on your OpenClaw version
OpenClaw's tooling and config layout vary between versions. Use whichever path your build supports — MCP if available, otherwise the raw API. Both hit the same endpoints behind the scenes.
See the MCP page for the server config and reference implementation.