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

Factset_spyderbot

FactSet · AI training crawlers · json

User-agent: Factset_spyderbot
Disallow: /


robots.txt token	`Factset_spyderbot`
User-agent contains	`Factset_spyderbot`
Operator	FactSet
Category	AI training crawlers
robots.txt	operator publishes no robots.txt statement
Verify by	no published verification method

What it is

FactSet's crawler, collecting data used in AI model training for its financial data and analytics products.

What blocking it costs you

Exclusion from a financial-data vendor's corpus. Relevant mostly to companies whose filings and disclosures are being read.

Full user-agent string

Factset_spyderbot

Allow it instead

User-agent: Factset_spyderbot
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=factset-spyderbot&s=client-dossiers'

/tools/verification-methods?crawler=factset-spyderbot
How do I prove a request really is Factset_spyderbot? 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://www.factset.com/ai
Machine copies: json · markdown
Policies that name this crawler: allow-all · block-ai-training · block-all-ai · maximum-ai-visibility