Guide

Meta's Muse agent: what your site can and can't see

Muse browses for its users in its own Chromium browser, and Meta says it shows up as the user's activity. What Meta has published about identifying it, and what to set now.

Meta launched Muse, a personal agent for adults in the US, on September 8. People message it in the Muse app or in WhatsApp, and Meta says it can "open a browser, fill out forms, and negotiate on their behalf." Muse is a different thing from Muse Spark, the model behind Meta AI in WhatsApp, Instagram, Facebook and Messenger.

Meta has described how the agent browses. It runs "a real up-to-date Chromium based browser" inside a virtual machine, and the part that reads pages works from "an accessibility tree snapshot of the page." On identity, Meta says: "When Muse browses the internet, it will appear as your activity." To your site, a Muse visit can look like your customer.

What Meta has published about identifying Muse

No user agent, IP range or signature for Muse, as of November 1, 2026. Meta's page for website owners lists five crawlers (FacebookExternalHit, Meta-WebIndexer, Meta-ExternalAds, Meta-ExternalAgent and Meta-ExternalFetcher), and Muse isn't one of them. The page doesn't mention signed requests.

One thing we can see: a file of five Ed25519 keys is live at meta.com/.well-known/http-message-signatures-directory, the address Web Bot Auth uses. Meta hasn't said what signs with it, and we haven't observed a signed Muse request.

Sites have gone both ways. Amazon barred Muse in September, and one of its reasons was that Muse doesn't identify itself as an AI agent while browsing. Walmart is a named Muse shopping partner, yet users reported Muse failing at its checkout, where a prove-you're-human step turned it away. Walmart told TechCrunch the blocks weren't intentional.

What to do now

If you want to be cited in Meta AI, allow Meta-WebIndexer. Meta says it helps "cite and link to sites in Meta AI responses."

If you want agents to finish a purchase or a signup, walk that flow yourself and look for the human check that would stop an automated browser.

Label your buttons and form fields. Meta says its browser reads the accessibility tree, so controls without accessible names give it less to work with.

Run fetchcheck on your key pages to see how your bot protection treats a signed agent. It signs as SitedexBot. It can't imitate Muse, which Meta says appears as its user's activity.

This page reflects Meta's published pages as read on November 1, 2026.

Check your pages with fetchcheck →