soldout/ akamai

Akamai,
out of your way.

One POST returns the sensor data and SBSD payload Akamai is waiting for. No browser, no farm, no per-site tuning.

POST /v3
# sensor data → a valid _abck
curl https://sold-out.dev/v3 \
  -H "x-api-key: $SOLDOUT_KEY" \
  -d '{ "pageUrl": "https://target.com/", "userAgent": "Mozilla/5.0 …",
       "abck": "<cookie jar>", "bmsz": "<cookie jar>",
       "script": "<sensor script>", "ip": "1.2.3.4" }'

200 OK
{ "payload": "3;0;1;0;3490105;Li9UX…", "context": "bSQ0lf…" }
/v3 · /sbsd
sensor + sbsd
3 majors
chrome 149, 150, 151
€2
per 1,000 solves
0 browsers
pure generation
What you get

Two endpoints. That is the whole surface.

Device selection, script analysis, challenge solving, session continuity: all of it happens on our side and stays there.

/v3

Sensor data

Posts back a payload that turns your _abck valid. The returned context carries the script analysis forward, so repeat calls in a session skip the expensive part.

/sbsd

SBSD body

Full SBSD payload from the script and the bm_so cookie, device-consistent for the whole session: one fingerprint, not a fresh one per request.

hyper

Keep your client

Already integrated? Point the base URL here. The Hyper request shape works unchanged, on /v3 and on the /v2/sensor path older clients use.

Start with €2 and a key.

Prepaid, per request, stops at zero. No card on file, no minimum, no call required. That one is only for unlimited.

Create account