Watch

Watch your domain

Name what you need kept current. We show which topics we read before any price, and we never charge for a topic we do not read.

Name your domain

Say what you need kept current, in your own words. We split it into topics, then check each topic against what we actually read. You see every topic and whether we read it before you see a price, and you are never billed for a topic we do not read.

Start a Watch

Configure any Watch and run it as often as you like, free and without a key. Saving it holds a slot: $20 a month for each saved Watch, as many as you want. Your first five Watches are on us while we open the doors. Save up to 5 Watches at no charge through December 31, 2026, one allowance per verified email address. No card is needed to start. After that a Watch is $20 a month, and only if you choose to keep it. Claiming it takes the API for now: this page has no form to confirm an email address yet. Self-issue a key (POST /api/keys, free, instant), then confirm an email address for it: POST /api/keys/verify with {"email"} and your key, and press the button in the email we send. Your next saves go into the opening slots. A saved Watch is tied to your key and recalled from here, the REST API or MCP, with what changed since it was last delivered to you. Refundable in full, any time — we return the month you're in.

1. Configure (free)

Start from a sample Watch (each one reads the Strait of Hormuz record)

This Watch reads: Strait of Hormuz transit: availability, safety and cost of passage. To have us watch something else, propose a topic below.

2. Your key

A saved Watch belongs to a key. Keys are free and instant; we keep only a fingerprint of it, so copy it somewhere safe.

3. Save it (the paid step)

Add a key first.

4. Your Watches: recall, see what changed, retire

Ask us to start keeping a topic

Need a topic we do not read yet? Commission it here, free. What happens next: we record it as a work order today; a matcher checks it daily against coverage we keep; we email you once when it's read, or with a plain status at 30 days. We give no date for coverage, because we do not have one.

Who uses a Watch

  • A maritime operator asks: Is passage through the Strait of Hormuz becoming more or less available, safe or costly, and why?
  • An energy desk asks: Is Gulf oil and gas supply at risk this month, and why?
  • An escalation analyst asks: Is the conflict between the United States and Iran escalating or easing?

A sample record: the Strait of Hormuz

This is one record we keep, shown as a sample of what a Watch reads. It is not a reading of your domain.

Agreement between publishers is not proof of the facts; a repeated error passes any count. Open “where from” on any claim to follow it to the original articles.

Strait of Hormuz

From the reporting ledger · newest report 11 Oct 2026

The ledger holds 2,322 claims about the strait: 0 corroborated, 4 reported by two, 2,318 single source. 43 of them were carried by several reports that all ran in one outlet or in the same words; repeated is not corroborated, so each counts by its separate sources. No claim on this record sits beside a live report that gives a different answer about the same incident. That counts live claims only, after any replacement, and only pairs our test could match incident for incident. 1 claim was replaced by a later report since 3 Sep; it is kept, marked, and not counted here. Another 80 look-alike pairs could not be matched incident for incident, so the test cannot say whether they differ. The newest of the best-supported are below.

No new claim carried by three or more separate reports since 28 Sep.

From the live Hormuz record: on Polymarket, “Will at least 10 ships transit the Strait of Hormuz on any day by October 31, 2026?” was priced at 22.5% when last seen (2026-10-11). That is Polymarket’s price, quoted as published. SigB publishes no probability of its own.

Set aside · 9 claims, each with why
  • Iraq is importing gasoline via Syrian port to bypass the closed Strait of Hormuz. Every report came from outlets that do not cover this subject.
  • An Iranian commercial ship was struck near Strait of Hormuz with 1 dead. Every report came from outlets that do not cover this subject.
  • One person was killed in a ship strike on the Strait of Hormuz. Every report came from outlets that do not cover this subject.

Replaced, never erased

When a later report replaces a claim, the record keeps the first one, marked, with the date and the reason.

No replaced claim could be read from the ledger for this build, so none is shown.

See every claim in the Hormuz record

Watch

The sample record (Strait of Hormuz), as data

GET claims_hormuz.json → counts, and the state of each viewpoint's sorted reading (build time)

{
  "ledger": {
    "computedAt": "2026-10-11T18:58:33+00:00",
    "newestSeen": "2026-10-11",
    "counts": {
      "kernel": 2322,
      "frames": 608,
      "retired": 10,
      "corroborated": 0,
      "two": 4,
      "single": 2318,
      "disputed": 0,
      "repeated": 43
    }
  },
  "viewpoints": [
    {
      "viewpoint": "Maritime operator",
      "asks": "Is passage through the Strait of Hormuz becoming more or less available, safe or costly, and why?",
      "sortedReading": {
        "state": "cannot-measure",
        "reason": "Sorting for this viewpoint is not published yet. It is built every day and checked against what happens next before we publish it. Until then nothing on this page is placed for one viewpoint over another; the claims below are the same for every reader."
      }
    },
    {
      "viewpoint": "Energy desk",
      "asks": "Is Gulf oil and gas supply at risk this month, and why?",
      "sortedReading": {
        "state": "cannot-measure",
        "reason": "Sorting for this viewpoint is not published yet. It is built every day and checked against what happens next before we publish it. Until then nothing on this page is placed for one viewpoint over another; the claims below are the same for every reader."
      }
    },
    {
      "viewpoint": "Escalation analyst",
      "asks": "Is the conflict between the United States and Iran escalating or easing?",
      "sortedReading": {
        "state": "cannot-measure",
        "reason": "Sorting for this viewpoint is not published yet. It is built every day and checked against what happens next before we publish it. Until then nothing on this page is placed for one viewpoint over another; the claims below are the same for every reader."
      }
    }
  ]
}

The ledger's own counts. No viewpoint has a published sorted reading yet, and each says so instead of showing a placement.

GET claims_hormuz.json → kernel[newest corroborated] where-from, folded one level

{
  "claim": "Iran has lodged a complaint with the United Nations over U.S. sanctions against its aviation sector, which have forced the cancellation of many flights across the region, state media reported Monday.",
  "status": "reported-by-2",
  "independentChains": 2,
  "repetition": null,
  "whereFrom": {
    "level": "where from",
    "label": "Where from",
    "relations": [
      {
        "role": "part of",
        "members": [
          "/event/hormuz/",
          "/record/"
        ]
      }
    ],
    "children": [
      {
        "level": "report",
        "label": "CBS News · first seen 28 Sep",
        "children": {
          "count": 1,
          "unfold": "expand=+1"
        }
      },
      {
        "level": "report",
        "label": "Gulfnews · first seen 28 Sep",
        "children": {
          "count": 1,
          "unfold": "expand=+1"
        }
      }
    ]
  }
}

The newest corroborated claim in the Hormuz reporting ledger, with its where-from tree folded below the first level. Each level names how to unfold the next, and every branch ends at a source link or a stated reason.