About AiSensy Bot

What is AiSensyBot?

AiSensyBot is the web crawler used by AiSensy to fetch the pages of a website that one of our customers has submitted as a knowledge source. When a business owner sets up an AI agent on AiSensy and points it at their website, AiSensyBot visits that site, reads its public pages, and uses the content to help the AI agent answer questions accurately. AiSensyBot identifies itself with the following User-Agent on every request:

AiSensyBot/1.0 (+https://aisensy.com/bot)

Why is it visiting my site?

If AiSensyBot is visiting your website, it's because someone with an AiSensy account — most likely you, a colleague, or a vendor who manages your site — entered your site's URL as a knowledge source for an AI agent. AiSensyBot only reads pages that are already public on your site, and it obeys the rules published in your robots.txt file under the AiSensyBot token. It does not submit forms, click buttons, log in, or attempt to access anything that isn't publicly reachable.

How to allow it (by User-Agent)?

If AiSensyBot is being blocked by your firewall or security plugin, the fix is usually a one-time allowlist rule based on its User-Agent. We recommend allowlisting by User-Agent rather than by IP address (see the note below on IPs). Here's how to do it on the most common platforms:

Cloudflare

1. Log in to your Cloudflare dashboard and select your site.

2. Go to Security → WAF.

3. Click Create rule (under Custom rules).

4. Set the rule to match: User Agent → contains → AiSensyBot.

5. Set the action to Allow (or Skip the rules that are blocking it, such as Bot Fight Mode / Super Bot Fight Mode).

6. Save and deploy the rule.

Wordfence / WordPress

1. In your WordPress admin, go to Wordfence → Blocking / Rate Limiting (or All Blocked IPs, depending on your Wordfence version).

2. Remove any existing block entries referencing AiSensyBot or the AiSensy crawler, if present.

3. Go to Wordfence → All Options → Advanced Blocking (or Whitelisted URLs/User-Agents, depending on version).

4. Add AiSensyBot as a whitelisted user-agent.

5. Save changes.

Sucuri

1. Log in to your Sucuri dashboard and select your site.

2. Go to Firewall (WAF) → Access Control.

3. Open the Whitelist tab.

4. Add a new rule to allow by User-Agent, entering AiSensyBot as the value.

5. Save the rule.

Generic nginx / Apache .htaccess

If your site is protected by a custom rule at the server level, ask your host or developer to add an allow rule for any request whose User-Agent contains AiSensyBot, placed above whatever rule is currently blocking it.

nginx (add to your server block, before the blocking rule):

if ($http_user_agent ~* "AiSensyBot") { set $block_bot 0; }

Apache .htaccess (add before the blocking directive):

RewriteCond %{HTTP_USER_AGENT} AiSensyBot [NC] RewriteRule .* - [L]

Your host or developer may need to adapt these snippets to fit alongside your site's existing rules — the important part is matching any User-Agent that contains AiSensyBot and allowing it through.

Prefer to allow by IP?

We can share AiSensyBot's current egress IP addresses on request — just reach out to your AiSensy contact or support. We don't publish them on this page because they can change over time, and a stale IP-based allow rule can silently start blocking us again. Allowlisting by User-Agent (AiSensyBot) is what we recommend, since it keeps working even if our IPs change.

Still stuck, or don't manage your own site?

If you're not the person who manages your website's hosting or security settings, please forward this page to your web host or developer — the steps above are written so they can copy and paste the fix directly.