Checking systems...

API Endpoints

API
Checking...
Database
Checking...
Forecast: Address (Houston)
Checking...
Forecast: Parcel (FL + NYC)
Checking...
Forecast: Tabblock (NYC + Houston)
Checking...
Forecast: Tract (Nationwide)
Checking...
Forecast: ZCTA (Nationwide)
Checking...
MCP Server (API)
Checking...

Data Coverage

EndpointCoverageRecords
/v1/forecast/unitFlorida + Houston + Seattle46M+ units
/v1/forecast/lotFlorida + NYC + Houston38M+ buildings
/v1/forecast/tabblockNYC + Houston67K tabblocks
/v1/forecast/tractFL + Houston + US (ACS)82K+ tracts
/v1/forecast/zctaNationwide20K ZCTAs
/v1/forecast/zip3Nationwide6.2K ZIP3s
/v1/forecast/countyNationwide72K rows
/v1/forecast/stateAll 50 states407 rows

Expected Cadence

This is the cadence we expect from the source systems. It explains how often the underlying data should move, separate from whether a materialized table or aggregate has been rebuilt.

SourceExpected cadenceWhy
ACS nationwideAnnualTracks yearly ACS release and retrain/backfill cycles.
Florida DORAnnualFollows yearly DOR / tax-roll file refreshes.
HCAD / Houston tractAd hoc to annualRefreshes when the assessor feed is re-ingested and the tract pipeline reruns.
Derived aggregatesWhen upstream data refreshesMaterialized tables inherit the latest source as_of_date instead of creating a new one.

Recent history in this browser

No local history yet. This panel fills after a few refreshes.

Docs and status navigation

Reference, guide, and status pages share this navigation so the public docs set stays consistent.

Ready to see your forecast?

Look up a home and see where its value may be headed over the next five years.