Conditions feeds
Geo-fenced event feeds for operators: what is happening in a place, on a topic, ranked by how much it matters — rebuilt hourly, over a rolling 7-day window.
What it is
dig.rest reads the world's news into a causal graph. The conditions feeds are a slice of that
graph cut for operational use: one JSON file per place × topic. Places are the 50
states, DC, and a national feed (52 in all); topics are logistics · insurance · permits.
Each event carries its title, date, the state it was placed in, the themes it matched, a corroboration count (how many distinct outlets carried the story, after collapsing re-reports of the same event), a source URL, and a priority score. Priority is built from tone, corroboration, theme class and recency — deliberately not from our causal turns, which reach only a small share of recent events and would rank the other 93% by their absence.
Every file carries a coverage block stating how many events were scanned, how many
were successfully placed, and the window actually served. A feed with nothing in it is still a
valid feed — an empty Wyoming file, not a 404, because "no news" and "no service" must not look
the same to a program.
How accurate is it — the measured answer
Hand-labelled precision at 20, on the national feeds, measured 2026-08-04. These are the real numbers, not a target:
| topic | precision@20 | what it is for | scored from |
|---|---|---|---|
logistics | 11/20 | disruption to the movement of goods and people | natural disaster · strike · blockade · armed conflict · protest, plus infrastructure themes |
insurance | 8/20 | loss events at county grain | natural disaster · crisis · casualty · displacement · terror themes |
permits | 3/20 | civic and regulatory friction for filming and construction | protest · strike · civic and regulatory themes |
Read that honestly. Logistics is usable with a human in the loop. Insurance is borderline. Permits is not good enough to buy yet, and the reason is structural rather than a tuning problem: our ingest gate admits crisis-shaped stories, so an ordinary council-agenda or filming-permit item never enters the corpus at all. The permits feed sees only civic events that were already heated. We would rather you read that here than discover it in week two.
Where the wrong rows come from
- law-firm press releases — they syndicate widely, and syndication is what our corroboration score rewards
- theme noise on listicles — GKG tagged a hidden-ice-cream-shops listicle as transport
- same story, different headline — collapsing these needs fuzzy title matching, which measured 77–85% and was refused — a deduplicator that is wrong one time in five merges distinct events
The top of each feed is markedly better than its tail — corroborated clusters (a wildfire and its evacuations, a port closure, a vessel strike) rank high and are reliably real. If you consume the top slice and treat the tail as leads rather than facts, the numbers above understate what you get.
What this is not
It is not a real-time wire, and it is not market data. News arrives on a rolling ingest and the feeds rebuild hourly; the economic series we carry alongside the graph are end-of-day publications pulled once a day from the publishing institutions, so every price or rate on this site is delayed by at least a session. Nothing here is suitable for trading, and nothing here is an underwriting decision. It is situational awareness with citations attached.
Evaluate it free
The feed endpoint is public and open — you can evaluate it right now, with no key, no account and no conversation with us:
curl 'https://api.ghalse.com/api/feed?geo=ca&topic=logistics'Read the precision numbers above, pull a few feeds, and judge it against your own knowledge of your own places. We would rather lose the sale to an honest evaluation than win it and be found out in week two.
Keys are paid
A key is a subscription. It does not unlock data you cannot already read — the public tier is genuinely open and stays that way. What a key buys is the commercial relationship around the feed: your calls counted per day, a named contact when something you depend on is about to change, and a claim on us if it breaks.
curl -H 'X-API-Key: <your key>' 'https://api.ghalse.com/api/feed?geo=ca&topic=logistics'Keyed requests carry a tier field and your own daily call count in the response, so
your usage is something you can check rather than something you take our word for.
What it costs
| price | $100 / month per key |
|---|---|
| term | monthly, cancel anytime |
| usage | [OWNER: pricing] included volume, and the rate beyond it |
How to get one
- Write to [email protected] with what you would use it for and which places and topics matter to you. If the honest answer is that the feed is not good enough for your use yet, that is the answer you will get — see permits, above.
- We send an invoice.
- Payment clears, and the key is minted and sent to you. Keys are issued by hand, one at a time, against a payment reference — there is no signup form and no self-serve checkout. That is slower than a form and it is deliberate at this size: every active key traces to a specific payment or a deliberately recorded free one.
The key is shown to you once, because only its hash is stored on our side. Lose it and we revoke and reissue — we cannot recover it, and neither can anyone who gets hold of our database.
Terms
Full terms: dig.rest/legal. Privacy: dig.rest/privacy. Source articles belong to their publishers; the feeds link to them and quote only titles.
Informational only — not financial, legal, or professional advice. Any action you take on this information is at your own risk. See /legal.