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. Claim it with the form on this page (Claim your free Watches, below), or through the API: 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

Claim your free Watches

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.

Give us an email address and we send one confirmation link. Open it and press the button on its page; only then does the allowance count. There is no account to make, no password and no card.

What we do with it: send one confirmation link, and, once you press the button on that page, keep the address as your key's contact and keep a one-way fingerprint of it, which is what the free allowance is counted by. It is never shared and never used for anything else. Confirming binds no payment to your key.

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 18 Oct 2026

The ledger holds 2,660 sentences about the strait. Grouped by the event they report, they make 1,651 events: 13 corroborated, 57 reported by two, 1,581 single source. The ledger also holds 854 sentences the event rule could not place; each counts on its own sources. 55 of those events 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. 2 claims were replaced by a later report since 3 Sep; they are kept, marked, and not counted here. The record also holds 105 pairs of similar claims the disagreement test could not compare role for role; the test cannot say whether they differ. The newest of the best-supported are below.

  • First reported 17 Oct

    Ten of the attacks occurred in the Strait of Hormuz, one in the Persian Gulf and one in the Gulf of Oman.

    Corroborated · 3 separate reports · 3 outlets · 3 sentences, one event

  • First reported 12 Oct

    Attacks on commercial shipping are spreading across the Gulf region, with two Indian seafarers missing after a drone struck a tanker off Oman on Sunday and another tanker hit by a projectile while exiting the Strait of Hormuz.

    Corroborated · 3 separate reports · 3 outlets · 3 sentences, one event

  • First reported 8 Oct

    A number of casualties have been reported after a tanker sailing off the north coast of Qatar was struck by multiple projectiles, the United Kingdom Maritime Trade Operations (UKMTO) agency has announced.

    Corroborated · 3 separate reports · 3 outlets · 3 sentences, one event

  • First reported 8 Oct

    Iranian attacks on tankers hit their highest level last week of any week since the U.S.-Iran war began, with the increased offensive coming shortly after shipping through Hormuz briefly touched pre-war levels in September.

    Corroborated · 3 separate reports · 5 outlets · 1 more carries the same wire story · 4 sentences, one event

  • First reported 29 Sep

    As presented by Araghchi, the plan calls for a seven-day cessation of hostilities across the region, including Lebanon; the release of at least $12bn in frozen Iranian assets; the lifting of sanctions on Iranian oil; and an end to the US naval blockade.

    Corroborated · 3 separate reports · 4 outlets · 4 sentences, one event

  • First reported 27 Sep

    Earlier on Saturday, President Donald Trump rejected a truce deal proposed by Iran that Tehran said could have reopened the Strait of Hormuz to shipping within a week.

    Corroborated · 4 separate reports · 4 outlets · 4 sentences, one event

  • First reported 15 Oct

    A surge in Iranian drone attacks on commercial ships appears to be weighing on Middle Eastern energy exports through the Strait of Hormuz, with 24 attacks reported so far this month.

    Reported by two · 2 separate reports · 2 outlets · 2 sentences, one event

  • First reported 15 Oct

    Around the same day, the Singapore-registered container ship GFS Pride was struck by an unidentified projectile while transiting the Strait of Hormuz.

    Reported by two · 2 separate reports · 2 outlets · 3 sentences, one event

From the live Hormuz record: on Polymarket, “Will there be no Hormuz agreement?” was priced at 90.6% when last seen (2026-10-18). 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.

The ledger keeps 2 replaced claims, each marked, and none is about the strait’s own reporting, so none is shown here. The record’s change log counts every replacement and shows the newest.

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-18T12:45:32+00:00",
    "newestSeen": "2026-10-18",
    "counts": {
      "kernel": 2660,
      "frames": 683,
      "retired": 11,
      "corroborated": 50,
      "two": 129,
      "single": 2481,
      "disputed": 0,
      "repeated": 55,
      "events": {
        "events": 1651,
        "corroborated": 13,
        "two": 57,
        "single": 1581,
        "couldNotMatch": 854,
        "rule": "event@2"
      }
    },
    "countUnit": "event",
    "standing": {
      "unit": "event",
      "unitMeaning": "event: the sentences the ledger's event rule (named in its eventRule header) groups as reports of one incident, counted together under the origins rule",
      "rule": "event@2",
      "sentences": 2660,
      "ladder": {
        "unit": "event",
        "counted": 1651,
        "corroborated": 13,
        "reportedByTwo": 57,
        "singleSource": 1581,
        "couldNotMatch": 854
      },
      "perSentence": {
        "unit": "sentence",
        "counted": 2660,
        "corroborated": 0,
        "reportedByTwo": 5,
        "singleSource": 2655,
        "notStated": 0
      },
      "fields": {
        "standing": "eventStatus",
        "separateReports": "eventOriginCount",
        "outlets": "eventOutletCount",
        "repetition": "eventRepetition",
        "eventKey": "eventKey",
        "sentencesInEvent": "eventSize",
        "match": "eventMatch"
      },
      "statement": "A kernel row that carries eventOriginCount is counted by its event (the rule named in the ledger's eventRule header): its standing is eventStatus and its count eventOriginCount, exactly as the page reads it. Its per-sentence status and originCount are kept beside them, unchanged. A row without the event fields is counted by its sentence: status and originCount. A row with disputedWith reads Contested whatever its count. A row whose eventMatch is could-not-match keeps its sentence count: could not match is not single source."
    }
  },
  "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": "Ten of the attacks occurred in the Strait of Hormuz, one in the Persian Gulf and one in the Gulf of Oman.",
  "status": "single-source",
  "independentChains": 1,
  "repetition": null,
  "standing": {
    "unit": "event",
    "level": "corroborated",
    "word": "Corroborated",
    "separateReports": 3,
    "outlets": 3,
    "repeated": null,
    "eventKey": "ev1:e09f0dc95d274f90",
    "sentencesInEvent": 3,
    "eventMatch": "matched"
  },
  "whereFrom": {
    "level": "where from",
    "label": "Where from",
    "relations": [
      {
        "role": "part of",
        "members": [
          "/event/hormuz/",
          "/record/"
        ]
      }
    ],
    "children": [
      {
        "level": "report",
        "label": "New York Post · first seen 17 Oct",
        "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. Its standing and counts are the ones this page shows, in the unit named (one sentence, or the event its sentences report); status and independentChains are the sentence's own, kept beside them. Each level names how to unfold the next, and every branch ends at a source link or a stated reason.