Skip to content

I-06Market Explain intelligence

Watchlist.Know what changed, field by field.

Star a broker and your browser keeps a fingerprint of its record. Next time you visit you see exactly which licence, cost or protection field moved since you last looked. Nothing leaves your browser.

Pick records Local only · no sample alerts

Live read

Checked 2 Nov 2026

Records to watch

every broker on file

Fields per record

typical; 35 to 55

Records with sources

at least one sourced field

Watching
0

in this browser

Computed in your browser from 42 records. Stored in your browser only. Nothing is sent anywhere.

01 / Watching

Watch a record.See exactly what changed next time.

Your browser keeps a fingerprint of every field: its status, its value and its source. On your next visit the live record is hashed again and compared, field by field.

  1. 01

    Star a record

    Pick any broker below, or use Watch on its record page.

  2. 02

    Its fields are hashed

    Status, value and source of every field, stored in this browser only.

  3. 03

    Come back later

    The live record is hashed again. Any field whose hash moved is listed.

Pick records to watch

0 of 42 watched

02 / Alert rules

Choose what counts.Everything else stays visible, uncounted.

A change only raises an alert when its field is in a category you keep. Changes outside them are still listed, greyed out, so nothing is hidden.

or only these

Saved in this browser. There are no push notifications or emails: changes show here and on the record page when you visit.

03 / Your data

Take it with you.A file, not an account.

Export the watchlist with its fingerprints as a JSON file, and import it in another browser to keep comparing against the same snapshot.

The file holds broker slugs, field hashes and dates. It holds no personal data and no field values.

  1. 01Watching a record stores, in this browser only, one short hash per field: FNV-1a over the field's status, its published value and its source link. Licence records, account rows and leverage rows are hashed one by one.
  2. 02On each visit the live record is hashed the same way. A field is changed when its hash differs, added when it is new, and removed when it is gone. Nothing else raises an alert, and there are no sample or test alerts.
  3. 03Only hashes are stored, never the values, so a removed field is named by its key. Mark as seen stores a fresh snapshot; the first-watched date is kept.
  4. 04Alert rules decide which changes are counted. Changes outside your categories are still listed, greyed out.
  5. 05There is no account, no server copy and no push notification. Clearing this site's data in your browser deletes the watchlist. Export it as a JSON file to move it to another browser.