What people build on the solver API
The pattern is the same in every case: clear the protection once per session with an API call, then collect public data with your own HTTP client. These are the workloads it suits best.
Use cases
- Price monitoringCollect public prices and stock from retail sites behind Akamai or Cloudflare without running browsers.
- Travel faresFare and availability searches on airline and travel sites behind Akamai, from plain HTTP.
- Ticket availabilityTrack public event availability and prices on ticketing sites behind Queue-it and reCAPTCHA Enterprise.
- Release monitoringWatch stock and release pages on retail sites behind Akamai and Queue-it from lightweight HTTP monitors.
Solvers
- Akamai solverSolve the Akamai sbsd challenge and the edge fingerprint screen without a browser.
- Akamai SBSD solverSend the sbsd challenge script, get the payload that answers it in about a second.
- Akamai edge solverClear the Akamai “Unusual Traffic Detected” fingerprint screen and get the real page’s cookies.
- Cloudflare solverGet a cf_clearance cookie from Cloudflare JavaScript Detections with one API call.
- Cloudflare JSD solverRun the Cloudflare JavaScript Detections exchange and return cf_clearance, without a browser.
- Queue-it BotDeflector solverSolve the Queue-it BotDeflector challenge from a flow token and get a ready-to-send redeem request.
- Ticketmaster tmpt solverBuild the reCAPTCHA Enterprise reload body that mints the Ticketmaster tmpt cookie.
Page updated .
Try it on your own target.
Login, copy a key, send one request. If the solve fails, it costs you nothing.