Start with the job.
Go as deep as you need.
Forecast a place, query a standardized panel, evaluate a model, or connect an agent. The quick paths stay small; the complete data and interface inventories remain one click away.
- documented assets
- 89
- available now
- 23
- benchmark assets
- 17
- REST paths
- 45
- MCP tools
- 44
The four most common tasks
Each guide starts with a working example and links into the full protocol reference only when you need it.
Get a forecast
Choose the most specific geography you have, from an address or parcel through tract, ZCTA, county, and state.
GET /api/v1/forecast/tract?geoid=48201231400Choose a forecast endpointReview standardized data contracts
Discover source assets, panel lineage, schemas, coverage, provenance, and geography crosswalks.
GET /api/v1/data/coverageBrowse the data catalogEvaluate a model
Use public forecast vintages, source manifests, and model-versus-baseline score tables with pinned provenance.
GET /api/v1/benchmarks/backtestsExplore benchmarksConnect an AI agent
Give agents the same forecast, catalog, lineage, provenance, and benchmark capabilities through structured MCP tools.
get_panel_lineage({ panel_id })See MCP toolsDiscover once. Switch interfaces without translating the data model.
- 1Public payloads first
Launch-ready aggregate forecasts, observations, and benchmarks lead every catalog view.
- 2Planned assets stay discoverable
Draft and metadata-only entries document their intended contracts and blockers.
- 3Restricted means governed
Holdbacks show policy status without exposing private, licensed, user, or operational records.
Documentation
Start with the job you need to do, then move into the complete interface reference.
Interfaces
REST, MCP, and typed client references.