Documentation · Letting our agent through your CDN · Vercel

Allowing our agent through the Vercel Firewall

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.

What to match

Match 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.

What you need

Setting it up

  1. 1. Add a rule

    Open the project, go to Firewall, open the menu and choose Configure, then Add New, Rule. Name it Allow Ottom agent.

  2. 2. Match our addresses and user 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/
  3. 3. Set the action to Bypass and publish

    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.

Checking it works

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.

When a scan is still blocked

Good to know

Vercel documentation

Menus move. If a name here no longer matches your dashboard, these are the pages we checked this guide against:

Questions

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.

The same rule for other providers, and why it is safe: the CDN guides.