Muse is an AI agent in the AI assistants and agents category, operated by Meta.
Muse is Meta's personal AI agent, which browses on a user's behalf to search, compare and fill in forms. It does not identify itself with a user agent of its own and runs mostly from cloud and CDN networks. Since around 12 October 2026 Meta has attached Web Bot Auth signatures to a share of its requests, but not all of them.
AI assistants fetch pages on demand when a user asks a chatbot or an agent to read, summarise or act on a URL. Each request is tied to a person, but the visit carries no ad impressions or analytics. Decide per agent whether the value is worth the load.
Muse does not identify itself with a user agent of its own, so its requests cannot be picked out by name. Transfon Security checks where each request comes from and how it behaves instead.
Muse does not read robots.txt and sends no user agent a rule could name. The rules below record your policy only. To act on Muse, use network and behaviour rules as shown in the next section.
User-agent: Muse Disallow: /
User-agent: Muse Disallow: /private/ Disallow: /search
User-agent: Muse Allow: /blog/ Disallow: /
User-agent: Muse Allow: / User-agent: * Disallow: /
User-agent: Muse group, Muse ignores your User-agent: * rules, so repeat any that should still apply.Treat robots.txt as a statement of your policy, and enforce it where requests arrive.
Muse reads pages for a person who asked an AI about them. The visit carries no ad impressions, so exclude it from ad requests and decide whether it may read paywalled content.
Transfon Security for publishersAgent visits can click through landing pages and fill in forms. Exclude Muse from conversions so campaign optimisation is based on people.
Transfon Security for advertisersAgents like Muse can compare prices and may soon place orders. Decide whether agents may reach checkout, and verify them before they do.
Transfon Security for e-commerceMuse can sign up, log in and call endpoints on a user's behalf. Rate limit it on sign-up and API routes, where fake trials and abuse start.
Transfon Security for SaaS and APIsMuse has no user agent of its own, so it does not appear by name in the Top Bots report and a User Agent rule cannot catch it. Transfon Security still sees each request's network and behaviour. Allow crawlers that do name themselves with a User Agent rule, or slow Muse-like traffic down with a rate limit decision rule.
Transfon Security
Muse is an AI agent in the AI assistants and agents category, operated by Meta. Muse is Meta's personal AI agent, which browses on a user's behalf to search, compare and fill in forms. It does not identify itself with a user agent of its own and runs mostly from cloud and CDN networks. Since around 12 October 2026 Meta has attached Web Bot Auth signatures to a share of its requests, but not all of them.
No. Muse does not read robots.txt and sends no user agent of its own, so there is no name a robots.txt rule could match.
Muse does not send an identifiable user agent, so it cannot be blocked by name. Block it by network and behaviour instead, for example by rate limiting cloud and data center traffic on login, form and checkout pages. In Transfon Security that is a decision rule, not a User Agent rule.
No. robots.txt cannot help with Muse: it does not read the file and sends no user agent of its own. Network and behaviour rules are the only real control.
AI assistants fetch pages on demand when a user asks a chatbot or an agent to read, summarise or act on a URL. Each request is tied to a person, but the visit carries no ad impressions or analytics. Decide per agent whether the value is worth the load.
Transfon Security identifies every bot in this directory in your traffic reports, flags fake search crawlers, and lets you allow, block or rate limit each bot.
Privacy, security, monetization, and performance insights. A few emails a month, no spam.