Discovery Signals
See how people and recognised AI systems are discovering The Tool Directory. Figures use a rolling 30-day window and appear only after enough activity has been recorded.
This counter appears after enough recognised AI requests have been observed.
Distinct recognised AI crawler or agent families seen during the same rolling window.
Privacy-conscious estimate of human visitor reach, excluding known bots and site administrators.
Shown when the site infrastructure supplies a reliable country code with the request.
What counts as an AI read?
An AI read is recorded when a recognised AI crawler or user-triggered AI agent fetches an individual tool profile, or when an AI client requests tool records through The Tool Directory’s public API. It is a measure of observable access to the directory’s product data.
It does not mean an AI assistant recommended, cited or endorsed a tool in a private conversation. We cannot see what a model says inside someone else’s chat.
How are AI systems identified?
Requests are classified using published user-agent signatures and other request information available to the site. User-agent strings can be spoofed, so these figures should be understood as observed request signals rather than proof that a provider indexed or recommended a particular page.
How is human reach counted?
Known bots are excluded. To avoid storing raw IP addresses, the site creates a one-way hash from limited request information and retains only the resulting identifier for the rolling analytics window. Country reach is counted only when the hosting or CDN layer provides a country code.
Why are small numbers hidden?
Signals appear publicly only after a minimum activity threshold is reached. Until then, the site shows that measurement is in progress rather than dressing tiny numbers up as meaningful traction.