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 is the paid step: $20 a month for each saved Watch, as many as you want. 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 8 Oct 2026

The ledger holds 1,922 claims about the strait: 4 corroborated, 27 reported by two, 1,891 single source. No claim on this record sits beside a report that gives a different answer. The newest of the best-supported are below.

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

From the live Hormuz record: on Polymarket, “Will 35-39 ships transit the Strait of Hormuz between October 5-October 11?” was priced at 6.5% when last seen (2026-10-08). 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.

From the Hormuz reporting ledger

Said on 22 Sept 2026: A senior Iranian official said Iran could reopen the Strait of Hormuz to Gulf shipping within seven days if the US fulfilled Tehran's demands to ease military pressure and lift an American blockade on Iranian ports, adding that Tehran had conveyed its latest proposal to Washington via mediators last week.

Replaced 8 Oct 2026 by: Iran could reopen the Strait of Hormuz to Gulf shipping within seven days if the US fulfilled Tehran's demands to ease military pressure and lift an American blockade on Iranian ports, the Iranian official said, adding that Iran had conveyed its latest proposal to Washington via mediators last week.

Why: A later report in the same thread replaced it. The first claim stays on the record, marked replaced. The ledger keeps 1 replaced claims this way.

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-08T18:22:37+00:00",
    "newestSeen": "2026-10-08",
    "counts": {
      "kernel": 1922,
      "frames": 530,
      "retired": 10,
      "corroborated": 4,
      "two": 27,
      "single": 1891,
      "disputed": 0
    }
  },
  "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": "US President Donald Trump has rejected an offer from Iran to reopen the Strait of Hormuz as Washington intensifies economic pressure on Tehran, including measures targeting banks and airlines.",
  "status": "corroborated",
  "independentChains": 6,
  "whereFrom": {
    "level": "where from",
    "label": "Where from",
    "relations": [
      {
        "role": "part of",
        "members": [
          "/event/hormuz/",
          "/record/"
        ]
      }
    ],
    "children": [
      {
        "level": "report",
        "label": "Al Jazeera · first seen 27 Sep",
        "children": {
          "count": 1,
          "unfold": "expand=+1"
        }
      },
      {
        "level": "report",
        "label": "Nairametrics · first seen 27 Sep",
        "children": {
          "count": 1,
          "unfold": "expand=+1"
        }
      },
      {
        "level": "report",
        "label": "BBC News · first seen 28 Sep",
        "children": {
          "count": 1,
          "unfold": "expand=+1"
        }
      },
      {
        "level": "report",
        "label": "Analyticsinsight · first seen 28 Sep",
        "children": {
          "count": 1,
          "unfold": "expand=+1"
        }
      },
      {
        "level": "report",
        "label": "Decrypt · first seen 28 Sep",
        "children": {
          "count": 1,
          "unfold": "expand=+1"
        }
      },
      {
        "level": "report",
        "label": "Tekedia · first seen 29 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.