Safe Official docs AI & LLM Bots

Lyrenth on-demand fetch

Operated by Lyrenth

Quick Facts

User-Agent:
AIWebIndex-Agent
Category:
AI & LLM Bots
Operator:
Lyrenth
Safety:
Safe
Blocking Impact:
Low - No effect on Google or Bing rankings
SEO Impact Score:
1/10
Official docs:
lyrenth.com

Confirmed by the operator

Lyrenth names AIWebIndex-Agent on its own documentation page, linked above. The token, purpose and robots.txt behaviour on this profile come from that page, re-checked on October 19, 2026.

What is Lyrenth on-demand fetch?

AIWebIndex-Agent fetches a page into Lyrenth's AI-readable web index when a customer asks for that exact URL.

Lyrenth says its index is not a model trainer. It identifies itself with the token AIWebIndex-Agent. Lyrenth documents it at lyrenth.com.

What happens if you block Lyrenth on-demand fetch?

Blocking it stops on-demand Lyrenth fetches; the scheduled crawler is AIWebIndex. No effect on Google or Bing.
Generally safe to allow; block it only if you do not want pages fetched on request.

Want to see whether Lyrenth on-demand fetch actually visits you? Read how do I monitor AI bot traffic to my website?

How to block Lyrenth on-demand fetch with robots.txt

<code>User-agent: AIWebIndex-Agent</code> - Matching is case-insensitive. Robots.txt is fetched from the root of each subdomain separately.

Block completely (robots.txt)
User-agent: AIWebIndex-Agent Disallow: /
Allow all (robots.txt)
User-agent: AIWebIndex-Agent Allow: /
Block private only (robots.txt)
User-agent: AIWebIndex-Agent Disallow: /private/ Disallow: /api/ Disallow: /admin/ Allow: /
Nginx server block
# Nginx: Hard-block Lyrenth on-demand fetch if ($http_user_agent ~* "AIWebIndex-Agent") { return 403 "Bot blocked"; }
Apache .htaccess
# Apache: Hard-block Lyrenth on-demand fetch SetEnvIfNoCase User-Agent "AIWebIndex-Agent" bad_bot Order Allow,Deny Allow from all Deny from env=bad_bot
Meta robots tag
<meta name="robots" content="noindex, nofollow">
X-Robots-Tag header
X-Robots-Tag: noindex, nofollow

Is Lyrenth on-demand fetch safe to allow?

Yes. Lyrenth on-demand fetch is a documented bot: Lyrenth publishes a page that names it and explains what it does.
Lyrenth gives three checks: the source IP is on lyrenth.com/bot/ip-ranges.json, the request carries a Web Bot Auth signature, and reverse DNS resolves under lyrenth.com.

What does Lyrenth on-demand fetch do?

From Lyrenth's own documentation.

  • AIWebIndex-Agent fetches a page into Lyrenth's AI-readable web index when a customer asks for that exact URL.
  • Not used to train AI models, according to the operator
  • Blocking it stops on-demand Lyrenth fetches; the scheduled crawler is AIWebIndex. No effect on Google or Bing.

Lyrenth on-demand fetch in context

Lyrenth on-demand fetch is a user-triggered agent operated by Lyrenth. In plain terms, it fetches a page when a person asks an assistant or app to open it. Our database files it under AI and LLM crawlers and ranks it Tier 3, mid-priority crawlers with a clear purpose but a smaller audience. 15 of the 104 AI and LLM crawlers in our database share this tier.

Its safety rating is safe and its blocking impact is low. So the decision about Lyrenth on-demand fetch rests on what you want from Lyrenth, not on its behaviour. How we rate safety and impact.

How site owners treat Lyrenth on-demand fetch

Our robots.txt study of the Tranco top 10,000 did not track AIWebIndex-Agent as a named token, so we do not publish an adoption figure for it. If you run a large site, your own logs are the best evidence of how often it visits.

Does it follow robots.txt?

Lyrenth on-demand fetch's operator says it follows robots.txt, so a correctly written Lyrenth on-demand fetch group is enough to control it.

Lyrenth crawlers and close alternatives

Lyrenth on-demand fetch is one of 2 Lyrenth crawlers in our database. A User-agent: AIWebIndex-Agent group controls Lyrenth on-demand fetch only; the other Lyrenth tokens below need their own lines.

  • AIWebIndex-Agent: this crawler (Tier 3)
  • AIWebIndex: Lyrenth AI Web Index, builds a search or answer index (Tier 2)

To give Lyrenth on-demand fetch the same answer as its siblings, stack User-agent: AIWebIndex-Agent with their lines above one set of rules; to treat Lyrenth on-demand fetch differently, give it its own group.

Other AI and LLM crawlers that do the same job (fetches a page when a person asks an assistant or app to open it) include ChatGPT Agent from OpenAI, ChatGPT Operator from OpenAI, ChatGPT-User from OpenAI, ChatGPT-User/2.0 from OpenAI, Claude-SearchBot from Anthropic, Claude-User from Anthropic. Deciding about Lyrenth on-demand fetch is usually a decision about the whole group, so check how your file treats these too.

We first recorded AIWebIndex-Agent on October 19, 2026. Lyrenth documents it on lyrenth.com, and we recheck that page before each release.

Which rule Lyrenth on-demand fetch actually follows

Lyrenth on-demand fetch reads exactly one group in robots.txt, the most specific one that names AIWebIndex-Agent, and never combines rules across groups. This short file shows the trap:

User-agent: *
Disallow: /private/

User-agent: AIWebIndex-Agent
Disallow: /drafts/
  1. Find the group. Lyrenth on-demand fetch looks for a group naming AIWebIndex-Agent. One exists, so it ignores User-agent: * completely.
  2. Apply only that group. It is refused /drafts/ and nothing else.
  3. The surprise. /private/ is open to Lyrenth on-demand fetch, because that rule lives in the * group it no longer reads. To keep it out of both, repeat Disallow: /private/ inside its own group.
Test yourself: does a rule under User-agent: * apply to Lyrenth on-demand fetch if the file also has a User-agent: AIWebIndex-Agent group?

No. Once a group names it, Lyrenth on-demand fetch reads only that group. Put every rule you want it to follow inside its own group.

Related: how AI engines choose their sources

Test yourself: will blocking Lyrenth on-demand fetch remove your pages from AI answers?

Often, yes. Lyrenth on-demand fetch is a user-triggered agent, so pages it cannot fetch can drop out of the answers or results it supports.

Test yourself: is User-agent: aiwebindex-agent the same as User-agent: AIWebIndex-Agent?

Yes. RFC 9309 makes user-agent matching case-insensitive. Paths are a different story: Disallow: /Blog/ does not block /blog/.

Should you allow Lyrenth on-demand fetch? Decide by situation

Recommended setting for Lyrenth on-demand fetch by type of site
If you are...Recommended setting
You publish content and want AI answers to cite itAllow it. Lyrenth on-demand fetch fetches pages for answers, so blocking it can remove you from them.
You license content and want to stop AI trainingBlocking it does not stop training, because Lyrenth on-demand fetch is a user-triggered agent. Block the operator's training crawler instead.
You run an online shopAllow it on product and category pages, which are the pages shoppers ask assistants about.
Your server is under load from botsRate-limit before blocking. It is rated safe in our database.

Check Lyrenth on-demand fetch on your own site

  1. Open /robots.txt on your domain and search for AIWebIndex-Agent. If it is not named, it follows User-agent: *.
  2. List the Disallow lines in the group Lyrenth on-demand fetch follows and test your key URLs against them; the longest match wins, and Allow wins a tie.
  3. Look beyond the file. A firewall or bot manager can refuse Lyrenth on-demand fetch even when robots.txt allows it, and that never shows in the file.
  4. Run our AI crawler tester to see how Lyrenth on-demand fetch and every other crawler we track are treated in one pass, including firewall refusals.

Common mistakes with Lyrenth on-demand fetch

The errors we see most often with Lyrenth on-demand fetch in the files and firewalls we test:

  1. Assuming a robots.txt rule will stop Lyrenth on-demand fetch. User-triggered fetches act for a person, and some operators say robots.txt may not apply to them. Check the operator's statement above.
  2. Blocking Lyrenth on-demand fetch as if it were a bulk crawler. It fetches one page because a person asked; blocking it means that person's assistant cannot read your page.
  3. Counting Lyrenth on-demand fetch visits as crawl volume. Each request maps to a real user question, which makes the paths it requests a useful signal of what people ask about you.

All three hide inside a file that looks correct, so check Lyrenth on-demand fetch from outside after every change.

Spotting Lyrenth on-demand fetch in your logs

robots.txt says what Lyrenth on-demand fetch may do; your access logs show what it actually did.

Count requests

On a server with standard Nginx or Apache logs, this counts matching requests per day (adjust the log path for your host):

grep -iE "AIWebIndex-Agent" /var/log/nginx/access.log \
  | awk '{print $4}' | cut -d: -f1 | sort | uniq -c

And this shows which paths it requested most, which is the quickest way to see whether your Disallow lines are being respected:

grep -iE "AIWebIndex-Agent" /var/log/nginx/access.log \
  | awk '{print $7}' | sort | uniq -c | sort -rn | head -20

Check the requests are genuine

Anyone can send the Lyrenth on-demand fetch user-agent, so confirm the source before acting on a match:

  • AIWebIndex-Agent: we hold no published IP list, so use reverse DNS where the operator documents a hostname and treat an unverifiable Lyrenth on-demand fetch request with caution.

Frequently Asked Questions

What is the official user-agent string for Lyrenth on-demand fetch?
The official user-agent string for Lyrenth on-demand fetch is: AIWebIndex-Agent. Use this exact string in robots.txt, Nginx, Apache, or Cloudflare firewall rules to target this bot. Matching in robots.txt is case-insensitive. Lyrenth gives three checks: the source IP is on lyrenth.com/bot/ip-ranges.json, the request carries a Web Bot Auth signature, and reverse DNS resolves under lyrenth.com.
Is Lyrenth on-demand fetch safe?
Yes. Lyrenth on-demand fetch is a documented bot: Lyrenth publishes a page that names it and explains what it does.
Will blocking Lyrenth on-demand fetch hurt my SEO?
Blocking it stops on-demand Lyrenth fetches; the scheduled crawler is AIWebIndex. No effect on Google or Bing.
How do I block Lyrenth on-demand fetch in robots.txt?
Add the following lines to your /robots.txt file:
User-agent: AIWebIndex-Agent
Disallow: /

This instructs Lyrenth on-demand fetch not to crawl any path on your site. To block only specific sections, replace / with the path (e.g., Disallow: /blog/).
Does Lyrenth on-demand fetch respect robots.txt?
Yes. Lyrenth says both of its user agents honour robots.txt the same way (RFC 9309, including Crawl-delay).
How do I verify if Lyrenth on-demand fetch is crawling my site?
Search your web server access logs for the string AIWebIndex-Agent (case-insensitive: grep -i "AIWebIndex-Agent" /var/log/nginx/access.log). Filter by user-agent in your log analytics tool (GoAccess, AWStats, etc.).

Related Bots