Skip to main content
Vercel BotID is Vercel’s bot protection for the API routes of sites hosted on its platform. It is built on Kasada, but it works differently from the challenge flows on the other Kasada pages: there is no 429, no /tl and no session token. Instead, protected requests carry a header named x-is-human, and the value is derived from a challenge script the page loads.

How to recognize it

Look at a protected request in your powhttp recording. If it carries an x-is-human header whose value is a JSON object, the endpoint is behind BotID. The page will also have loaded a script named c.js from a path on the same site with random segments and a query string like ?i=0&v=3&h=www.example.com. That is the challenge script.

The flow

1

Fetch the challenge script

GET the c.js URL from your recording, through your session, with the script headers the browser used. Keep the body exactly as received. It is limited to 1 MiB.
2

Ask Roolink for the header

Call /botid with the script body. Roolink returns a JSON object with six fields: b, v, e, s, d and vr. That object, serialized as JSON, is the header value. Counts against your Kasada plan.
3

Send the protected request

Make the request with the browser’s headers for that endpoint from your recording, and put the JSON string in x-is-human in the position the browser had it. Sites built on Vercel commonly send x-path and x-method alongside it; if your recording shows them, send them too, with the endpoint’s path and method.

When to generate a new header

Generate a fresh header when you start a new session, when the IP changes, or when a protected request answers 429. Within one session a header can be reused for a while, but generating one per request is cheap and removes the guesswork. The script itself changes rarely; refetch it when a header built from your cached copy starts being refused.

Request fields

Troubleshooting

Compare the request with the browser’s in powhttp: the x-is-human position, the x-path and x-method values, the content type, and the origin. If they match, the verdict is about the IP or the rest of the fingerprint; change proxy session and try again.