Sensei tried to read your site and got a 403.

In your Cloudflare dashboard, go to Security → Bots → Configure. Add a custom rule that allows requests where User-Agent contains `Sensei`. If you're on the free plan and don't have custom rules, disable the 'Block AI Scrapers and Crawlers' toggle for your marketing subdomain.

# Cloudflare WAF custom rule expression
(http.user_agent contains "Sensei/1.0") or (http.user_agent contains "+https://asksensei.dev/bot")

Vercel Dashboard → your project → Firewall → Custom Rules. Add a rule that permits requests matching our User-Agent and set the action to Allow. If you're using an allowlist-mode firewall (default-deny), include our UA string in the allowlist.

# Vercel Firewall custom rule
when   user_agent contains "Sensei/1.0"
action allow

Create a Web ACL rule with a string-match condition on the User-Agent header. Match `Sensei/1.0` (case-insensitive) and set the action to Allow — place it above any Block rules for bots.

# AWS WAF managed rule exclusion (CloudFront)
Priority: 10 (before any default-deny rules)
Match:    Header "User-Agent" contains "Sensei/1.0"
Action:   Allow

If you're self-hosting behind nginx or a custom reverse proxy that blocks unknown bots, add an exception for our User-Agent in your server block.

# nginx — allow Sensei ahead of any bot-blocking rules
map $http_user_agent $is_sensei {
    default                   0;
    "~*Sensei/1\.0"          1;
}

server {
    if ($is_sensei) { set $allow_bot 1; }
    # ... your existing bot-blocking rules here
}