curl -s https://www.pathwren.workers.dev/crawler/meta-webindexer.json # this page, as JSON
No key, no account, no handshake — every page here has a JSON twin one hop away. Machine doors: 6 keyless GET tools · documents.json · changes · llms.txt · openapi.json · agent card · mcp · a2a
Meta · AI search crawlers · json
User-agent: Meta-WebIndexer Disallow: /
| robots.txt token | Meta-WebIndexer |
| User-agent contains | Meta-WebIndexer |
| Operator | Meta |
| Category | AI search crawlers |
| robots.txt | operator publishes no robots.txt statement |
| Verify by | no published verification method |
Per Meta's crawler documentation, Meta-WebIndexer navigates the web to improve the quality of Meta AI's search results. It is a third Meta token alongside Meta-ExternalAgent and Meta-ExternalFetcher, and the newest of them.
You leave the index Meta AI answers from across Facebook, Instagram and WhatsApp — the largest assistant install base there is. A robots.txt that names the two older Meta tokens does not cover this one.
Meta-WebIndexer
User-agent: Meta-WebIndexer Allow: /
A question about this page, answered by a call you can make right now — no key, no account, no JSON-RPC, nothing to assemble. The query string is already filled in with this page's own subject.
curl -s 'https://www.pathwren.workers.dev/tools/verification-methods?crawler=meta-webindexer&s=client-dossiers'
/tools/verification-methods?crawler=meta-webindexerEvery parameter above is a value the endpoint reads, not an address it visits: nothing is fetched on your behalf. Called without any parameter, each endpoint returns its own specification instead of an error. All of them.
Operator documentation: https://developers.facebook.com/docs/sharing/webmasters/web-crawlers/
Machine copies: json ·
markdown
Policies that name this crawler:
allow-all · block-all-ai · allow-ai-search-only · maximum-ai-visibility