Skip to main content

Account and saves

Reading the site never requires an account. The capture moment — watching an actor, following a forecast, saving a search — is where you sign in. Registration is free (login, email, password); every save syncs across devices.

The cabinet lives at dgw.tmarket.io/account: profile, watchlist, follows, saved searches, notifications, usage and API keys.

Watchlist​

Press Watch on an actor dossier and the actor joins the watchlist. The point of watching is the return loop: the watchlist band reports what happened on your watched actors since your last visit — new claims, decisions and events — each entry linking to the record. Watching a claimant works the same way from claim pages: their new claims land in the band.

Below the list, You may also watch suggests similar actors — each row names the watched anchor it came from; Watch adds it in place, ✕ hides it for good.

Follows​

Press Follow on a forecast you need to track. Followed forecasts sit in the follows list, and changes report to the inbox so you do not have to poll the board.

Saved searches​

Run a search, save it, re-run it from the account in one click. Saved searches keep the query and the kind filter; they are the fast path back to a slice of the wire you care about.

Place watch​

Place pages carry a watch action for the geographic slice: watch a country or region and its new records report to the inbox like actor watches do.

Inbox​

The inbox collects notifications for the loops above: new activity on watched actors, changes on followed forecasts and watched places. Rows are grouped per source, link to the record, and clear as you visit.

Usage​

The usage page is the honest free-plan meter: server counts of what the account holds (watched actors, followed forecasts, saved searches) plus this-browser counters (record reads, saved-search runs) that reset with the month. Nothing is hidden behind a paywall today.

API keys​

API keys give programs the same read surface the site has. Keys are dgw_live_… secrets shown once at creation (stored hashed; the list shows only the masked prefix), carry per-key rate budgets (120/min, 10k/day) with a usage drawer that meters them, and can be revoked any time — a revoked key answers 401 revoked_api_key. Keys authorize read-only routes only — the public GET families — and never account routes. See the public API reference for what a key can reach; reads without a key stay open under a per-IP budget.