RageCaptcha exposes a short request/poll JSON REST API for programmatic captcha solving. You submit a task with POST /create-task (returns HTTP 202 with a task_id), then poll POST /check-task every 1–2 seconds until the solve completes. This keeps every HTTP hop short — a slow solve never holds a Cloudflare request open. We currently support the PopularCaptcha family only — Standard and Enterprise variants, proxied or proxyless. Failed solves return HTTP 500 and are automatically refunded. Balance top-ups are non-refundable and we do not issue free trial credits.

Every request is authenticated with a clientkey — a unique secret developer token issued from your dashboard. Treat it like a password, keep it server-side, and rotate immediately if leaked.

Submit a captcha task. The API validates, atomically charges your balance, persists the task, and immediately returns HTTP 202 with a task_id. The solver request starts in the background — poll /check-task for the result.

curl -X POST https://api.ragecaptcha.com/create-task \
  -H "Content-Type: application/json" \
  -d '{
    "clientkey": "your-api-key",
    "data": {
      "task": "PopularCaptchaTokenProxyless",
      "sitekey": "captcha-site-key",
      "siteurl": "https://example.com"
    }
  }'

Poll for the result of a task. Prefer POST — it keeps the API key out of URLs and access logs. Poll every 1–2 seconds until status is no longer processing. A failed solve returns HTTP 500 with one of the three documented solver errors and is automatically refunded. The GET form /check-task?clientkey=...&task_id=... is also accepted.

curl -X POST https://api.ragecaptcha.com/check-task \
  -H "Content-Type: application/json" \
  -d '{
    "clientkey": "your-api-key",
    "task_id": "5d54269e-8cdf-40fb-a94c-912adca99ac8"
  }'

Fetch real-time balance for your account. The alias GET /getBalance returns the same response. Poll before dispatching large batches or wire into your billing alerts.

curl -G https://api.ragecaptcha.com/balance \
  --data-urlencode "clientkey=your-api-key"

Blueprints are namespaced by captcha family. Today only PopularCaptcha is live — Standard tier handles the everyday token; Enterprise tier targets Enterprise-tier sitekeys. Future families will slot in under their own namespace.

Application-level errors use { "error": "..." }. Framework-level 404 / 405 responses use { "detail": "..." }. Every response includes an X-Request-ID header. Failed solves are refunded automatically.