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

Linguee

1 crawler(s) · json

Crawler	Token	Category	robots.txt
Linguee Bot	`Linguee Bot`	AI training crawlers	compliance disputed

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=linguee&s=client-dossiers'

/tools/verification-methods?crawler=linguee
How do I prove a request really is one of Linguee's crawlers? Every crawler Linguee operates in one call, each with the verification method that operator publishes for it.

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.

Documentation: https://www.linguee.com

This page as markdown: /operator/linguee.md — the same text, no markup to strip, no JavaScript, no key, CC0. Every page here has one: add .md to any address (also .mdx, <page>.html.md, <page>.html.mdx), or send Accept: text/markdown to this one. All of them in a single index: /sitemap.md.