Skip to main content
Interfere sends a small set of automated HTTP requests on behalf of the workspaces that use it. Each request carries the same identity, so website and API operators can recognize, allow, or block it.

​
How it identifies itself

Every request sends the user agent Interfere/1.0 (+https://interfere.com/bot). Match on the stable token Interfere/. In production, requests are also signed with Web Bot Auth (HTTP Message Signatures with Ed25519). Each signature covers the authority, method, path and query, carries tag="web-bot-auth", and expires after 60 seconds. Requests send Signature-Agent: "https://interfere.com", and the public keys are published at https://interfere.com/.well-known/http-message-signatures-directory. Interfere-owned address space is listed at https://interfere.com/ips.json; requests sent from shared cloud infrastructure rely on the signature instead.

​
What it requests and on whose behalf

The bot does not crawl, index, or follow links. It only calls the specific endpoints below, each triggered by a workspace’s configuration or by an investigation that workspace runs.

​
How often

Requests are made on demand, one at a time per action, with a 10-second timeout for most lookups. Interfere does not schedule recurring scans of third-party sites. Company logos are fetched once per company and theme and served from Interfere’s storage afterward. Redirects are not followed automatically: each new destination is validated and, in production, signed again.

​
robots.txt

Interfere does not fetch or apply robots.txt, because it does not crawl. Every request targets a specific API endpoint that a workspace connected, a public registry, or a provider API Interfere integrates with. To refuse Interfere’s requests, block the user agent token Interfere/ or the verified bot in your firewall, or disconnect the server from the workspace.

​
Contact

Report a problem with Interfere’s automated traffic through https://interfere.com/.well-known/security.txt.