Developer API

Castle Solver API

Generate valid Castle tokens for X/Twitter and Android apps like DailyPay. One request, ~50 ms.

$0.00055Per token
Web + Android (APP)Both live now
Pricing

Only pay for what you use

Buy credit once, spend it per token. No subscription, no monthly bill — your balance only drops when you generate.

  • $0.00055 per token — $0.55 per 1,000 requests
  • Credits never expire, no minimums
  • 100 req/sec · live balance and usage dashboard
Read the API reference →
Pay-As-You-Go · Live

Metered usage

$0.00055 / token

Prepaid credit, billed per token. Unused balance never expires.

  • Web & Android token generation, live now
  • Bearer-key auth · per-key usage stats
  • Real-time balance + usage dashboard
  • No minimums, no expiring credits
EST · 100,000 req ≈ $55.00 / month
Pipeline

How it works

Send one request, Castle Solver computes a valid token, and you attach it to your request to the Castle-protected site or app.

  1. Send a request
    POST /generate/web or /generate/android with the target site or app identity. Full bodies live in the API reference.
  2. We generate the token
    A fresh, valid Castle token is computed server-side in ~50 ms — no browser farm, no manual challenges.
  3. Use the token
    Attach the returned token and headers to your request to the target site or app.
POST /generate/web Bearer key
curl -X POST https://castle.botwitter.com/generate/web \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -d '{
    "user_agent": "Mozilla/5.0 (Windows NT 10.0; Win64; x64)",
    "domain": "x.com"
  }'
Bearer key required. Send Authorization: Bearer YOUR_API_KEY with every request — get one from the plan above.
Reference

Frequently asked

Short answers to the questions developers ask most before wiring Castle Solver in.

It generates a valid Castle token so your automation can pass the Castle challenge on the target site or app. X/Twitter (web) and DailyPay (Android) work out of the box; for other sites or apps we haven't tuned yet, contact us.
Send your API key as Authorization: Bearer YOUR_API_KEY. A key is required.
/generate/web returns a browser Castle token; /generate/android returns a native Android app token as X-Castle-Request-Token + X-Castle-Client-Id. Both endpoints are live.
Android supports Castle-protected apps in general. A native Android application token is derived from the app identity (public_key, app_label, app_version, app_version_code) plus a signed session_id. Reuse the returned session_id to keep the same device, or omit it to mint a fresh one. DailyPay is our example app; for your specific app or any other, contact us to add or confirm support.
Pay-as-you-go at $0.00055 per token against a prepaid balance — no plans to pick. Larger top-ups earn bonus credit (see Pricing).
Pass the domain field to target a Castle-protected site — x.com and signin.rockstargames.com are supported out of the box (keys listed in the API reference). Other sites are supported too — contact us for ones we haven't tuned yet, or for other apps and custom needs.
Around 50 ms typical per token.