AI crawlers / UseAI

UseAI

UseAI has 25 recorded blocks in October 2026, or 0.4%, and 21 files naming it. Its operator is unclear in the community reference.

Who runs UseAI?

FactUseAI reference entry
Operator“Unclear at this time.”
Purpose“AI Assistants”
Does UseAI obey robots.txt?“Unclear at this time.”
Frequency“Unclear at this time.”
Cloudflare managed list for UseAINo

These facts quote the stored community ai.robots.txt reference.

“UseAI is a web crawler associated with Use AI, a platform that provides an AI workspace where users can chat with AI models, research the web, and perform various tasks. …”

The stated role here is an AI assistant. A site can welcome a page fetch prompted by a person while declining the collection of that text to build future models.

How many sites block it?

The 25 files blocking the whole site account for 0.4% of 6,171 readable robots.txt files. We found its name in 21 User-agent lists, a 0.3% share. Without a whole-site Disallow: / block, 6,146 files remain.

At the top 1,000 ranks, we could read 552 files. Naming covers 4, a 0.7% share, and blocking covers 4. Blocking is more common among the leading sites, at 0.7%. Elsewhere, 5,619 readable files give 21 blocks, or 0.4%.

Readable filesNamed byNamed shareBlocked byBlocked share
UseAI, all ranks210.3%250.4%
UseAI, top 1,00040.7%40.7%
UseAI, remaining ranks170.3%210.4%

Only whole-site blocks recorded against this crawler’s name count here. Rules addressed to every crawler are outside this count. Of 25 blocks, 5 do not also appear in our count of files naming it. The overlap between naming and blocking is 20 files. Naming without a whole-site ban accounts for 1, and 6,150 files never name it. We ignore capitalization and repeated names.

How to block or allow it

Add these lines to robots.txt at your site root. For UseAI, the robots.txt standard gives a named group priority over User-agent: *.

Block the whole site

User-agent: UseAI
Disallow: /

Allow access

User-agent: UseAI
Allow: /

It's the 148th most-named crawler of the 171 we counted in the crawler index.

How we counted

For UseAI, on 19 October 2026, we requested robots.txt from Tranco’s top 10,000 sites. An 8-second wait or a file over 262,144 bytes ended a read. Only available files we could read enter the percentages. Parsing includes files read again, through scripts/robots_2026_08_06.py (robots.py at app commit 07104ff). See the full survey method.

Common questions

Does a User-agent line mean it is blocked?

The 21 files that mention its name do not all record a whole-site ban. Those without one total 1.

What do the top-ranked sites show?

Its name appears in 0.7% of readable leading files and 0.3% overall. Blocking affects 0.7% in the leading group and 0.4% in all ranks.

Which nearby entry can I compare?

QwenBot is named by 20 files and blocked by 20, or 0.3%. For this crawler, 21 files name it and 25 block it, a 0.4% share.