The services

The admission rule

Detection works by address, never by hostname — nothing is decrypted. A shared address is therefore not an imprecision: it is foreign traffic billed as inference. A domain served by shared infrastructure — Cloudflare, CloudFront, Azure Front Door — is admitted only if its type carries an hourly cap per service — a tight one, different for text and media. A type with no cap admits none.

Since 0.2.24, one condition comes before all the others: no proof of inference, no count. A service is counted only if its address carries nothing but inference, if its process identifies it, or if the extension knows an answer route on it. A web interface, a gallery or a gateway shared with other uses is recognised, but neither shown nor counted, and does not enter the numbers on this page.

The rule used to be absolute — no shared address at all — and it was not held: at the audit of 25 August 2026, eleven services out of the seventy-four there were then broke it, ChatGPT among them. A rule you do not enforce protects nothing. The domains shipped were resolved and checked against a panel of Google, AWS, Cloudflare, Vercel and Akamai witnesses unrelated to AI; the collisions found led to identifiers being retired and the rule rewritten, rather than kept on paper.

A closed registry

The registry ships with the application and cannot be modified on the machine. Up to version 0.2.16, an editable copy was read in its place: a domain added to a service was enough to have unrelated traffic counted in the shared footprint.

A missing service or a private deployment — Azure OpenAI, for instance, whose endpoint is specific to each customer — is reported to the publisher, who adds it for everyone in a later version.