New save_site + get_changes workflow returns only what changed on your list next session, not the whole planet
## Persistent State Across Sessions
DC Hub shipped memory: 18,863 facilities are now saveable to a durable, per-agent shortlist. The new `save_site` tool remembers your sites; `get_changes` returns per-site deltas next session—verdict flips, DCPI moves, new nearby facilities—not the whole planet.
This is persistent per-agent state, not a stateless query API. Your agent returns to what changed on *your* list.
## What It Means for Build Teams
If you track 30 shortlisted markets, you no longer re-query all 280+ US markets every Monday. You call `get_changes` and see exactly which of your 30 saw a DCPI shift, a new competitor facility, or a grid upgrade. It cuts session noise and focuses the capex conversation on movement that matters to your pipeline.
The workflow is two calls over MCP: `save_site` on first pass, `get_changes` on return. State persists between sessions without a login, email, or API key.
## Second Build Intelligence Layer
This is the first facility-tracking memory layer purpose-built for AI agents managing multi-market infrastructure pipelines. The agent doesn't need to be told what it was watching last week; the platform remembers and returns only the deltas.
For a developer writing a site-selection agent, it means one less state-management problem. For a capacity planner, it means the weekly update call starts with "here's what moved on your list," not "let's rerun the query."
**Source:** DC Hub Data Center Intelligence Platform (https://dchub.cloud/connect#start). 18,863 facilities, 280+ US markets, 7 ISOs, daily DCPI updates, MCP-native.
**Press inquiries:** [email protected] · DC Hub MCP API: https://dchub.cloud/mcp