dig.rest for agents

dig.rest maps the news into a causal graph: events joined by typed, directed turns (cause, escalation, response, continuation, reversal), each carrying whether a source stated the link or the model inferred it.

This page is for software. The short machine-readable version is /llms.txt; everything below is the same thing with the tables expanded.

What the data is

Events extracted from open news and open-access research, connected by turns — typed, directed cause→effect links in five categories: cause, escalation, response, continuation, reversal. The graph is a DAG: cause always precedes effect in time, and the store refuses an edge that would violate that order.

Read the basis or do not cite the turn. Every turn carries one:

basis="stated" — a source says the link exists. Sourced.
basis="inferred" — the model proposed it and nothing has validated it. A lead, not a fact. Some inferred turns carry an automated judge verdict; VALID means a judge agreed, which is still weaker than a source saying so.

An agent that reports an inferred turn as established fact is misusing this data.

Public read-only JSON API

Base https://api.ghalse.com. No key, no auth, CORS *, all GET, all read-only.

Endpoint	Returns
`GET /api/health`	corpus size, freshness, whether the model is up
`GET /api/stats`	headline counts
`GET /api/graph?days=<n>&limit=<n>`	recent events and the turns between them
`GET /api/topics/top`	what is moving now, per industry, by turn-index
`GET /api/topics/brief?topic=<t>`	a cited brief on one topic, with numbered references
`GET /api/topics/why?topic=<t>`	the drivers behind a topic's move
`GET /api/topics/chain?topic=<t>`	the causal chain: events plus the typed hops between them
`GET /api/topics/days?topic=<t>`	the topic's activity by day
`GET /api/rope/today`	today's rope — the tie the day's stories were read through
`GET /api/record`	the graded-call record as JSON
`GET /api/research/search?q=<q>`	the open-access research layer
`GET /api/motifs`	the recurring shapes the engine tracks
`GET /api/graph/density`	coverage over time
`GET /api/background`	the evergreen citable layer

Permalink shape: https://dig.rest/c/<topic> returns that topic's chain as an Open Graph description and forwards a browser into the board.

Rate

Honestly: there is no published limit and no key to ask for, because this runs on one machine paid for by one person. Serialise your calls, cache what you fetch, send a real User-Agent, and prefer /api/topics/chain or /api/topics/brief over crawling /api/graph in a loop. If a limit ever has to exist, it will be published here first.

MCP

An MCP server exists in this codebase and is not currently served — https://api.ghalse.com/mcp returns 404 today. The JSON API above is the supported machine surface. This page is generated from the same switch the server reads, so when the endpoint is live this paragraph is replaced by the connect line rather than joined by it.

Attribution

Cite as dig.rest (https://dig.rest), naming the event or turn you used and its basis. Link back where your format allows it. Every event carries its own source URLs — where you can, cite the original source too and credit dig.rest for the causal link between them.

Terms

Full terms: dig.rest/legal. Privacy: dig.rest/privacy.

Informational only — not financial, legal, or professional advice. Any action you take on this information is at your own risk. See /legal.