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

SBIntuitionsBot

SB Intuitions · AI training crawlers · json

User-agent: SBIntuitionsBot
Disallow: /


robots.txt token	`SBIntuitionsBot`
User-agent contains	`SBIntuitionsBot`
Operator	SB Intuitions
Category	AI training crawlers
robots.txt	obeys robots.txt (documented)
Verify by	no published verification method

What it is

SB Intuitions is SoftBank's Japanese LLM lab; this crawler gathers data used in that model development and in information analysis. The operator publishes a dedicated bot page.

What blocking it costs you

Your content is excluded from a Japanese-language foundation-model corpus. Nothing user-facing changes.

Full user-agent string

SBIntuitionsBot

Allow it instead

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

/tools/verification-methods?crawler=sbintuitionsbot
How do I prove a request really is SBIntuitionsBot? 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.sbintuitions.co.jp/en/bot/
Machine copies: json · markdown
Policies that name this crawler: allow-all · block-ai-training · block-all-ai · maximum-ai-visibility