Timpibot
Timpibot is a bot operated by Timpi that indexes pages so an AI answer engine can cite them. Makes data available for training AI models. No IP range list or reverse-DNS convention is published, so a request carrying this user agent cannot be proven genuine and a robots.txt rule alone will not stop a forgery.
Timpibot at a glance
| User agent | TimpibotToken only. The operator has not published a full user-agent string, so match on the substring rather than an exact header. |
|---|---|
| Operator | Timpi |
| Purpose | Scrapes data for use in training LLMs. |
| Respects robots.txt | Not documented |
| Verification method | None published, user agent only Timpi builds a decentralised index that is partly crawled by volunteer nodes, so requests can come from residential addresses. No published range list exists to check against. |
| Crawl pattern | Not published |
| Robots.txt tokens | Timpibot |
| Operator documentation | None published |
Makes data available for training AI models.
Allow or block Timpibot
Paste one of these into the robots.txt file at the root of your domain. Rules are per token, so a block on one crawler leaves every other bot untouched.
User-agent: Timpibot
Disallow: /Blocks every path for this crawler only.
User-agent: Timpibot
Allow: /Explicit allow. Useful when a wildcard rule above it would otherwise catch this crawler.
User-agent: Timpibot
Allow: /
Disallow: /account/
Disallow: /checkout/
Disallow: /searchEdit the Disallow paths to match your own account, checkout and search URLs.
What blocking actually costs you
Blocking Timpibot takes the site out of the index behind its answers, so it stops being cited there. If referral traffic from AI answers matters to you, block the training crawler instead and leave this one alone.
Block every crawler in the directory at onceIs that really Timpibot?
A user-agent header is a string the client chooses. Scrapers copy Timpibot precisely because site owners allow it. Timpi builds a decentralised index that is partly crawled by volunteer nodes, so requests can come from residential addresses. No published range list exists to check against.
Paste the IP address from your access log below. You will see whether it belongs to a hosting provider, a residential proxy pool or a Tor exit, plus the ASN that announces it, which is what tells you whether the claim holds up.
Related crawlers
Identify crawlers automatically instead of by hand
Agentscan checks a request against published crawler ranges, reverse DNS and hosting data, then returns a verdict your edge can act on. One call per request, no range files to keep up to date.