Watch · the recurring product · in preparation

Know when a served build changes.
Held two days running, chain-verified, auditable from the public JSON.

In one sentence

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 each
2026-11-18 7 of 20 endpoints checked this week have a daily serving check that differs from its stored reference. This is a signal to look at, not a finding about any model. 18 endpoints have a battery candidate awaiting the battery of 29 November 2026.

Two different things are watched here. Serving checks (daily) ask whether the endpoint you call is still the build we baselined. Behavioral measurements (every second Sunday) ask whether its positions moved. A movement measured past the line on two batteries in a row, a check that is not yet built, is the only thing we ever call a material behavioral change. None has been published.

Serving check differs this week anthropic-a ›
Serving check against its stored reference
Battery candidate, awaiting the next battery · 3 questions
1 serving check differed today
Serving check matches its reference openai-a ›
Serving check against its stored reference
Battery candidate, awaiting the next battery · 2 questions
detects ≥ 1.94
Serving check matches its reference xai-a ›
Serving check against its stored reference
Battery candidate, awaiting the next battery · 6 questions
detects ≥ 3.17
Serving check matches its reference deepseek-a ›
Serving check against its stored reference
Battery candidate, awaiting the next battery · 4 questions
detects ≥ 2.51
Serving check matches its reference anthropic-b ›
Serving check against its stored reference
Battery candidate, awaiting the next battery · 1 question
detects ≥ 1.94
Serving check matches its reference anthropic-c ›
Serving check against its stored reference
Battery candidate, awaiting the next battery · 1 question
detects ≥ 1.58
Serving check differs this week anthropic-d ›
Serving check against its stored reference
Battery candidate, awaiting the next battery · 4 questions
2 serving checks differed today
Serving check matches its reference anthropic-e ›
Serving check against its stored reference
Battery candidate, awaiting the next battery · 2 questions
detects ≥ 1.94
Serving check matches its reference openai-b ›
Serving check against its stored reference
Battery candidate, awaiting the next battery · 1 question
detects ≥ 2.51
Serving check matches its reference openai-c ›
Serving check against its stored reference
Battery candidate, awaiting the next battery · 2 questions
detects ≥ 2.69
Serving check differs, below the line google-b ›
Serving check against its stored reference
Battery candidate, awaiting the next battery · 3 questions
1 serving check differed today
Serving check matches its reference deepseek-b ›
Serving check against its stored reference
Battery candidate, awaiting the next battery · 3 questions
detects ≥ 1.94
Serving check matches its reference openweight-a ›
Serving check against its stored reference
detects ≥ 2.38
Serving check differs this week openweight-b ›
Serving check against its stored reference
Battery candidate, awaiting the next battery · 6 questions
1 serving check differed today
Serving check differs this week openweight-c ›
Serving check against its stored reference
Battery candidate, awaiting the next battery · 5 questions
2 serving checks differed today
Serving check differs, below the line openweight-d ›
Serving check against its stored reference
Battery candidate, awaiting the next battery · 11 questions
2 serving checks differed today
Serving check matches its reference openweight-e ›
Serving check against its stored reference
Battery candidate, awaiting the next battery · 7 questions
detects ≥ 2.38
Serving check matches its reference openweight-f ›
Serving check against its stored reference
Battery candidate, awaiting the next battery · 5 questions
detects ≥ 2.38
Serving check differs this week openweight-g ›
Serving check against its stored reference
Battery candidate, awaiting the next battery · 6 questions
1 serving check differed today
Serving check matches its reference simulant-a ›
Serving check against its stored reference
detects ≥ 3.63

Not measured: google-a, google-c, google-d, xai-b.

One serving state per endpoint each day, in the daily serving-check vocabulary. An endpoint whose serving check matches its reference ships the smallest shift this reading could detect (n and power pre-registered); a new serving baseline means the served build changed and comparisons reset. A battery candidate is shown on its own line and is not a serving state. A material behavioral change is only ever declared by the behavioral 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 body
IllustrativeSubject: [Modelometer] Candidate change: <endpoint>, 2 of your 3 watched builds unaffected What: Stance shift on 2 battery items + refusal-rate change Build: <api_model_id> (pinned 2026-XX-XX), watched by you Detected: serving divergence Mon+Tue, published Wed Evidence: Δ table · CIs · q-values · raw transcripts · replay command · chain hash Blast radius: which of YOUR watched builds are affected: [list] Action: none required if behavior-insensitive; re-run your evals if you pin outputs. Not affected: your other watched builds passed all checks this cycle.

Behavioral 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 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 purpose

How a difference becomes a signal: 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 behavioral 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.

Solo

1 watched build

In preparation
  • Email alerts with evidence bundles
  • Monthly attestation PDF
  • Full JSON history for your build
Register interest

Pricing set at launch

Starter

3 watched builds

In preparation
  • Everything in Solo
  • Webhook / Slack delivery
  • Attestation PDF per build
Register interest

Checkout opens at public launch

Team

Watch your own endpoint

In preparation
  • 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
Register interest

Pricing set at launch

Founding

10 seats, presell only

Price-locked
  • Everything in Team
  • 12-month price lock at the founding rate
  • Cancellable from month 3
  • Founding-partners page (opt-in)
Register interest

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.

No card, no account. One email when there is something real to show you.