Known-Agents
Known-Agents is a live-fetch agent operated by Known Agents. It does not crawl the web on a schedule. It hits your site only when an end-user asks the underlying AI a question that requires fresh information from a specific page.
Traffic is bursty and unpredictable. A single trending topic can send hundreds of Known-Agents requests in an hour, then nothing for days. Each request typically reads one or two pages, not your whole site.
Allowing Known-Agents is how your content becomes part of Known Agents's answers. Blocking it means users asking that AI about your topic will be answered using someone else's content instead.
See Known-Agents on your own site
Match the User-Agent header on incoming requests against the pattern below.
regex
For higher confidence, also verify the source IP against the operator's published ranges. UA strings can be spoofed; IP ownership is harder to fake.
Renders JavaScript
Sometimes
IP verification
User-Agent only
Crawl frequency
Burst, user-driven
Honors robots.txt
Yes
Honors Crawl-delay
Varies
Known Agents runs 3 bots in total. Each one is a separate user-agent so you can allow or block them independently.
DevOps & Monitoring
1Task Automation
1Live-Fetch AI
1- Known-AgentsYou are here
Should I let Known-Agents through?
In most cases, yes. Live-fetch agents drive citations inside AI answers. Allowing keeps your content in the conversation. If volume gets noisy, rate-limit it before you block it outright.
Does blocking Known-Agents affect my Google rankings?
No. Known-Agents fetches a page only when a user is actively asking Known Agents a question. It has nothing to do with how Google or Bing rank you. The cost of blocking is that Known Agents can't quote your content in its answer.
How do I confirm a request is really from Known-Agents?
Look at the User-Agent header in your access logs and match it against the strings listed above. Worth knowing that the User-Agent is easy to fake, so this check tells you "the traffic claims to be Known-Agents", not "the traffic is genuinely Known-Agents". If you need stronger guarantees, look for a reverse-DNS check or wait for Known Agents to publish IP ranges.
Does a Known-Agents visit count as a real user visit?
Sort of. There is a human asking Known Agents a question on the other end, but they never load your page in their own browser. They see whatever Known Agents quotes back, usually a snippet plus a citation link. Count it as upstream attention rather than as a session.
How is Known-Agents different from Known Agents's other bots?
Known Agents splits work across multiple user-agents so site owners can decide on each one independently. Training crawlers, live-fetch agents, search indexers, and agentic browsers each get their own name. Worth scanning the rest of the Known Agents family above to see which ones actually matter for your site.
What's the cleanest way to control Known-Agents?
Two layers. Robots.txt for the polite crawlers that read it, and rules at your CDN or edge for the ones that don't. Rankly's Agent Experience handles both from a single config, so you can allow, block, rate-limit, or serve a stripped-down version per bot. Agent Analytics handles the observation half so you know which bots are actually worth a rule.