Timpibot

Crawls pages for Timpi's decentralized index, which is also used as LLM training data.

Timpibot is operated by Timpi and classified here as model training. These agents collect text and images that may end up in a training corpus. Disallowing one withholds new content from the next model. It does not withdraw anything collected before the disallow, and it does not remove the site from any answer engine.

Disallowing timpibot withholds content crawled from that point on from Timpi's training data. It does not withdraw pages collected in earlier crawls, it does not reach copies already sitting in third-party datasets, and it does not remove the site from any answer surface.

robots.txt token

timpibot

Operator

Timpi

Purpose

Model training

Honors robots.txt

yes

Documentation

https://timpi.io/

Timpibot/1.0 (+http://timpi.io/crawler)

curl -A 'Timpibot/1.0 (+http://timpi.io/crawler)' https://example.com/

Replace the host with your own. A 403, a challenge page or an empty body means the edge is blocking the agent whatever robots.txt says.

Timpi runs no other agent in this registry.

Does blocking Timpibot remove me from the Timpi index?

No, not by itself. Timpibot collects content for training, not for the index that answers questions. Timpi operates no separate answer crawler in this registry, so there is no answer surface to lose here. Content collected before the disallow is not withdrawn.

How do I verify Timpibot requests are genuine?

Timpi publishes neither reverse DNS names nor address ranges for Timpibot, so a request carrying this user agent cannot be authenticated. The string is trivially spoofed and is routinely reused by unrelated scrapers. Treat it as a hint, rate-limit by source address, and do not grant it access you would not grant an anonymous client.

See whether your robots.txt admits Timpibot today, and whether your edge agrees with it.