InterfaceDeltaBot

Identity and purpose

InterfaceDeltaBot identifies itself as InterfaceDeltaBot/1.0 (+https://interfacedelta.com/bot). It records bounded factual observations of public, machine-readable software interfaces so changes can be compared over time.

Passive boundaries

The bot uses bounded HTTPS GET requests plus bounded, read-only MCP initialization and listing POST exchanges. It does not authenticate, submit forms, invoke tools, follow declared destinations onto another hostname, execute discovered software, or use model inference to decide protocol correctness.

Initial operating limits

Controlled operation permits one concurrent observation, no more than one scan start per hostname per rolling day, four scan starts per rolling hour and 24 per rolling day globally. A scan may make at most 12 requests, including robots.txt and redirects. Requests to a host are spaced by at least one second, and scan starts by at least 30 minutes. Responses, time, retries, and daily source traffic are also bounded. Operation is disabled unless explicitly activated.

Robots and redirects

Proactive observation retrieves and caches robots.txt through the same HTTPS, DNS, address, redirect, request-budget, and pacing controls. Missing robots.txt permits access. Explicit disallow rules are honored. Malformed responses, timeouts, and temporary server failures fail closed. Redirects and secondary protocol requests must retain the exact canonical hostname; DNS CNAME resolution does not itself change the requested application hostname.

Request suppression

An operator may ask us to stop future proactive observation of a hostname by emailing support@interfacedelta.com. Please identify the hostname and your relationship to it. We record suppression rather than deleting historical public evidence. A request already in flight may finish; suppression is rechecked before every subsequent network request.