Checking systems...
| Endpoint | Coverage | Records |
|---|---|---|
| /v1/forecast/unit | Florida + Houston + Seattle | 46M+ units |
| /v1/forecast/lot | Florida + NYC + Houston | 38M+ buildings |
| /v1/forecast/tabblock | NYC + Houston | 67K tabblocks |
| /v1/forecast/tract | FL + Houston + US (ACS) | 82K+ tracts |
| /v1/forecast/zcta | Nationwide | 20K ZCTAs |
| /v1/forecast/zip3 | Nationwide | 6.2K ZIP3s |
| /v1/forecast/county | Nationwide | 72K rows |
| /v1/forecast/state | All 50 states | 407 rows |
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.
| Source | Expected cadence | Why |
|---|---|---|
| ACS nationwide | Annual | Tracks yearly ACS release and retrain/backfill cycles. |
| Florida DOR | Annual | Follows yearly DOR / tax-roll file refreshes. |
| HCAD / Houston tract | Ad hoc to annual | Refreshes when the assessor feed is re-ingested and the tract pipeline reruns. |
| Derived aggregates | When upstream data refreshes | Materialized tables inherit the latest source as_of_date instead of creating a new one. |
No local history yet. This panel fills after a few refreshes.
Start with the job you need to do, then move into the complete interface reference.
REST, MCP, and typed client references.