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

TikTokSpider

ByteDance · AI training crawlers · json

User-agent: TikTokSpider
Disallow: /


robots.txt token	`TikTokSpider`
User-agent contains	`TikTokSpider`
Operator	ByteDance
Category	AI training crawlers
robots.txt	compliance disputed
Verify by	no published verification method

What it is

A second ByteDance crawler identifying with TikTok, collecting page content for the same family of models.

What blocking it costs you

Little to lose unless TikTok search referral matters to you.

Full user-agent string

Mozilla/5.0 (compatible; TikTokSpider; ttspider-feedback@tiktok.com)

Allow it instead

User-agent: TikTokSpider
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=tiktokspider&s=client-dossiers'

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