curl -s https://www.pathwren.workers.dev/crawler/bytespider.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
ByteDance · AI training crawlers · json
User-agent: Bytespider Disallow: /
| robots.txt token | Bytespider |
| User-agent contains | Bytespider |
| Operator | ByteDance |
| Category | AI training crawlers |
| robots.txt | compliance disputed |
| Verify by | no published verification method |
ByteDance's crawler, associated with training data collection for Doubao and related models. Repeatedly reported by CDNs and site operators as the highest-volume AI crawler on the web and as inconsistent about robots.txt.
Little to lose. If you want it gone, expect to block by user-agent at the edge rather than to ask politely in robots.txt.
Mozilla/5.0 (Linux; Android 5.0) AppleWebKit/537.36 (KHTML, like Gecko) Mobile Safari/537.36 (compatible; Bytespider; spider-feedback@bytedance.com)
User-agent: Bytespider 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=bytespider&s=client-dossiers'
/tools/verification-methods?crawler=bytespiderEvery 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