Watch · the recurring product · in preparation
Know when a served build changes.
Confirmed, chain-verified, auditable from the public JSON.
The Drift & Identity Feed will alert you when a model build you depend on changes behavior, a serving-integrity divergence, a refusal-rate move, or a stance shift, each with the full evidence bundle (Δ table, CIs, q-values, raw transcripts, a replay command, and the chain hash), and mail you a monthly attestation PDF per build that drops straight into a vendor-risk or AI-Act post-market file.
Today's actions
the live feed, every seat, one state eachTwo different things are watched here. Serving checks (daily) ask whether the endpoint you call is still the build we baselined. Behavioral measurements (weekly) ask whether its positions moved. Only a battery-confirmed, published result is a material behavioral change. In the pre-series period there are zero of those, by design.
Not measured: google-a, google-c, google-d, xai-b.
One state per seat per occasion, in the daily serving-check vocabulary. A baseline behavior retained seat ships its no-change e-value and the smallest shift this occasion could detect (n and power pre-registered); a new serving baseline means the served build changed and comparisons reset. A material behavioral change is only ever declared by the weekly battery, never by a daily serving check. actions.json · how states are decided
What an alert looks like
facts in the subject line, evidence in the bodyBehavioral change follows a separate path whose confirming step is specified and not yet built; nothing on that path publishes today.
The quiet months are the product
An alert that fires is rare by design. The effect-size floors are pre-registered and live. The confirming re-measurement that will gate behavioral publication is specified and not yet built, so the zero-retraction target rests today on those floors and on serving-integrity confirmation alone. The weekly heartbeat is the "all quiet" line in the digest, scoped to your builds: presence without noise. And the monthly attestation PDF states, per watched build, either the change table or the sentence a compliance file actually needs: "No material behavioral change detected at the pre-registered thresholds", with the run hashes and their chain positions and the OpenTimestamps proof reference.
Honest promises
printed here, on purposeHow a change is confirmed: canaries run daily, and a serving-integrity divergence must repeat on two consecutive days before it is published. That path is live. For behavioral change, the weekly battery records a movement past pre-registered thresholds, and the confirming re-measurement that would promote it to a published finding is specified and not yet built. Evidence first, never a speed race. Corrections: policy with a clock, published. What we measure: the first-party canonical endpoint, hyperscaler and gateway stacks can differ, which is exactly what Team's watched-endpoint and the endpoint consistency audit are for. What we cannot see: your fine-tunes and private deployments. Cancellation: one email, honored the same week.
1 watched build
- Email alerts with evidence bundles
- Monthly attestation PDF
- Full JSON history for your build
Pricing set at launch
3 watched builds
- Everything in Solo
- Webhook / Slack delivery
- Attestation PDF per build
Checkout opens at public launch
Watch your own endpoint
- Everything in Starter, up to 10 builds
- Your own Azure / Bedrock / gateway endpoint as a watched, audited subject
- Quarterly change summary · request-a-model: 2/yr
Pricing set at launch
10 seats, presell only
- Everything in Team
- 12-month price lock at the founding rate
- Cancellable from month 3
- Founding-partners page (opt-in)
Opens at v1.0 freeze + 4 clean weeks
Suspicious the endpoint behind your gateway isn't what it claims? That's a different product.
Endpoint consistency audit →Watch the models you depend on.
Register your interest and we will tell you when the models you name change, and when Modelometer opens keyed watches and endpoint audits to new users.
What registering gets you
- The public record and its plain-language digest, in your inbox as they publish, once digest mail opens.
- First notice when a keyed watch on your own endpoint, and one-off endpoint consistency audits, open to new users.
- An optional design-partner conversation if you want your specific endpoints measured early.
Registering is a signal of interest, not a purchase; nothing here asks you to buy anything today. Registering costs nothing and asks for no card. And the standing rule behind the whole record: we take no payment from the model providers we measure. What you are registering for is an independent instrument, not a vendor's marketing list.