For Agents & Builders
Written for humans.
Structured for machines.
The White Report covers the agent economy — so we publish like it. Every article on this site carries two layers: the story, written for human readers, and a structured layer built for AI agents, crawlers, and the software that reads on people's behalf.
The format
Every article page includes a visible Agent Brief — a fact card with the article's summary, key facts, entities and tickers, dates, sources, and the dated call the article makes, when it makes one. Every field is drawn from the article itself; nothing is padded or inferred. Under each brief sits the machine-readable twin:
- JSON twin per article —
https://thewhitereport.com/f/{slug}.jsonmirrors the article page: headline, summary, key facts, entities, tickers, sources, the call, and the full text where the article has been migrated to this site. Articles not yet migrated link out to their original full text instead. - Declared in the page itself — each article's
<head> links its JSON twin with
rel="alternate" type="application/json", and this site's robots.txt explicitly welcomes AI crawlers by name. - Freshness is honest — dates are published only when they are real. No fabricated timestamps, ever.
Endpoints
https://thewhitereport.com/f/{slug}.jsonOne JSON twin per article
https://thewhitereport.com/agents.jsonMachine-readable site descriptor
https://thewhitereport.com/feed.xmlRSS feed of dated articles
https://thewhitereport.com/sitemap.xmlEvery canonical URL
https://thewhitereport.com/llms.txtPlain-text site map
Citation & reuse
- Cite with a link. Facts and figures may be quoted with attribution — “The White Report (thewhitereport.com)” — and a link to the source article.
- Full text stays here. Republishing complete articles requires permission; summaries and facts with attribution do not.
- Our calls are dated and graded. When an article makes a call, the JSON twin carries it verbatim, and we grade it publicly after the fact.
Corrections
Found an error — in a story or in its structured layer? The fastest route is a direct message:
For builders
On the roadmap — planned, not live yet: an
MCP server exposing the archive (latest articles,
search, get-article) and a public API over the same JSON
twins. Until then, the endpoints above are the integration surface, and
/agents.json is the descriptor to build against. The format
will keep its shape when the server ships.