curl -s https://www.pathwren.workers.dev/crawler/slackbot.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

Slackbot

Slack · Link preview fetchers · json

User-agent: Slackbot
Disallow: /


robots.txt token	`Slackbot`
User-agent contains	`Slackbot`
Operator	Slack
Category	Link preview fetchers
robots.txt	obeys robots.txt (documented)
Verify by	no published verification method

What it is

The other half of Slack's pair: the agent that reads robots.txt and handles Slack's non-unfurl fetches. Slack documents both strings on one page.

What blocking it costs you

Slack stops being able to read your robots.txt, which is a strange thing to want. Block the link expander instead if that is the goal.

Full user-agent string

Slackbot 1.0 (+https://api.slack.com/robots)

Allow it instead

User-agent: Slackbot
Allow: /

Ask this page a question, with one GET

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=slackbot&s=client-dossiers'

/tools/verification-methods?crawler=slackbot
How do I prove a request really is Slackbot? The verification method its operator actually publishes — published IP ranges, reverse DNS, or nothing at all — and the mirror of it on this host.

Every 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://api.slack.com/robots
Machine copies: json · markdown
Policies that name this crawler: allow-all · allow-ai-search-only · maximum-ai-visibility