How to allow, verify or block Muse (Meta)
No documented way to allow Muse specifically. Retailers that partner with Meta, such as Walmart, work through the deal, not a header.
Checked October 20, 2026. Meta plans an encrypted Confidential VM for Muse later in 2026, but has not published agent identification for site owners.
How it identifies itself
| Signal | Value | Documented by the maker |
|---|---|---|
| user-agent | muse- (prefix) | No, third-party only radar.cloudflare.com |
- Allow it
- No documented way to allow Muse specifically. Retailers that partner with Meta, such as Walmart, work through the deal, not a header.
- Verify it
- There is no reliable check. Amazon and bot-detection firm Fingerprint say Muse does not identify itself or sign requests, and Meta does not document the "muse-" user-agent prefix Cloudflare Radar lists.
- Block it
- Cloudflare Radar lists "User-Agent: muse- / Disallow: /" as a robots.txt directive. Because Meta does not document it, expect behavior-based bot defenses to do most of the work, which is how Amazon handled it.
robots.txt lines for Muse (Meta)
Copy the group you want for muse-. The most specific matching group wins over your * group.
Let it in
User-agent: muse-
Allow: /Keep it out
User-agent: muse-
Disallow: /What we can and can't confirm
1 of the 1 signals above come from third parties, not from the maker, so treat them as hints. Matching a user agent string alone is easy to fake. A published IP list or a signed request is the stronger check, where the maker offers one.