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

EchoboxBot

Echobox · Corpus and dataset builders · json

User-agent: EchoboxBot
Disallow: /


robots.txt token	`EchoboxBot`
User-agent contains	`EchoboxBot`
Operator	Echobox
Category	Corpus and dataset builders
robots.txt	operator publishes no robots.txt statement
Verify by	no published verification method

What it is

Collects data supporting Echobox's AI-driven social and email distribution products, which publishers use to schedule and target their own content.

What blocking it costs you

Publishers using Echobox get worse scheduling decisions about your articles. No compliance statement is published.

Full user-agent string

EchoboxBot

Allow it instead

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

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