What does Bypass skip?
Vercel documents it as passing the request over any custom or managed rule. It applies only to requests that match both conditions.
Documentation · Letting our agent through your CDN · Vercel
On Vercel, our agent is let through with one custom rule in the project’s Firewall: it matches our addresses and a user agent that starts with our token, with the action Bypass. Bypass passes the request over your custom and managed rules, and is available on every plan.
OttomAgent/https://ottom.io/agent/ips.jsonMatch both, never the user agent alone: anyone can send our user agent, but only we send it from those addresses. The current addresses are also listed on our agent page.
Open the project, go to Firewall, open the menu and choose Configure, then Add New, Rule. Name it Allow Ottom agent.
Add the condition IP Address with each address from the file. Add a second condition, joined with and: User Agent, starts with, and the value below.
OttomAgent/Choose Bypass, then Save Rule, Review Changes and Publish. A rule with Bypass cannot be set in vercel.json, so it has to be made here.
Run a scan of your store from your Ottom dashboard. When the rule works, the report has no bot protection finding and the agent reaches your products. In the Firewall’s traffic view, our requests show the rule as matched with the action Bypass.
Check the rule was published, not only saved, and that it lists every address in the file.
Menus move. If a name here no longer matches your dashboard, these are the pages we checked this guide against:
Vercel documents it as passing the request over any custom or managed rule. It applies only to requests that match both conditions.
The same rule for other providers, and why it is safe: the CDN guides.