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 SI agents, crawlers, and the software that reads on people's behalf.

Use in Muse

This site's MCP server is also a Muse custom connector. If you use Muse, paste this setup prompt into a chat and Muse connects it for you — read-only, no account and no API key:

Add The White Report as a custom connector. Its MCP server is already running at https://thewhitereport.com/mcp.php — read-only, no account and no API key. It has five tools: get_latest, search_articles, get_article, get_ticker, get_scoreboard. Connect it, confirm the tools list, then show me the latest scoreboard.

Short form: “Add The White Report as a custom MCP connector: https://thewhitereport.com/mcp.php — no sign-in needed, it's public and read-only.” Builders: the wire format is described by an OpenAPI 3.1 spec of the endpoint, and the connector icon is the badge at https://thewhitereport.com/assets/icon-512.png (512×512 PNG).

After connecting, try: “What's the latest from The White Report?” · “What calls has The White Report made, and how did they grade?” · “Give me The White Report's current market snapshot.”

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}.json mirrors 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 SI 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

https://thewhitereport.com/llms-full.txtFull-text companion: surfaces, calls & scoreboard, and the complete article index

https://thewhitereport.com/calls.jsonEvery dated public call, its grade date, and its grade

https://thewhitereport.com/mcp.phpMCP server (live) — get_latest, search_articles, get_article, get_ticker, get_scoreboard

https://thewhitereport.com/agents/openapi.yamlOpenAPI 3.1 description of the MCP endpoint

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:

DM on Instagram DM on X

For builders

Live now: the White Report MCP server at https://thewhitereport.com/mcp.php (server white-report, v0.1.0) exposes the archive to any MCP client — get_latest, search_articles, get_article, get_ticker and get_scoreboard (every dated call we have made, its grade date, and its grade). Still on the roadmap: a public API over the same JSON twins. The endpoints above remain the integration surface, and /agents.json is the descriptor to build against.