Forecast guide

    Choose the right endpoint for your use case

    Homecastr forecasts are available at multiple geographic levels. Start with the most specific data you have access to, then fall back to broader geographies as needed.

    Looking for model inputs or evaluation data instead? Use the data catalog or benchmark guide.

    Quick decision tree

    1

    Do you have an address?

    Use the address endpoint to geocode and get a forecast.

    /api/v1/forecast
    2

    Do you have parcel data?

    Use parcel/lot endpoints for the most detailed forecast available.

    /api/v1/forecast/lot or /api/v1/forecast/unit
    3

    Do you have a Census geography?

    Use tabblock or tract endpoints for neighborhood-level analysis.

    /api/v1/forecast/tabblock or /api/v1/forecast/tract
    4

    Use the broadest available geography.

    Fall back to ZCTA, county, or state for regional market data.

    /api/v1/forecast/zcta, /api/v1/forecast/county, or /api/v1/forecast/state

    API endpoints

    Address forecast

    Look up a forecast by street address. The API geocodes the address and returns a neighborhood-level H3 forecast.

    Input
    address
    Endpoint
    /api/v1/forecast

    Best for: User-facing address lookups, web maps, mobile apps.

    Parcel/Lot forecast

    Get the most detailed forecast available: property-level parcel data with lot-specific forecasts.

    Input
    account ID (acct)
    Endpoint
    /api/v1/forecast/lot

    Best for: Real estate professionals, appraisers, detailed property analysis.

    Unit forecast

    Get unit-level forecasts within a parcel, optionally including sibling units.

    Input
    account ID + include_siblings
    Endpoint
    /api/v1/forecast/unit

    Best for: Multi-unit properties, condo analysis.

    Tabblock forecast

    Highest-resolution public geography forecast. Census-defined tabulation block level.

    Input
    15-digit GEOID20
    Endpoint
    /api/v1/forecast/tabblock

    Best for: Granular geographic analysis when parcel data is unavailable.

    Tract forecast

    Census tract-level forecast. Stable endpoint backed by an RPC wrapper.

    Input
    11-digit GEOID20
    Endpoint
    /api/v1/forecast/tract

    Best for: Neighborhood-level analysis, market comparisons, fallback when parcel data is unavailable.

    ZCTA/ZIP forecast

    ZIP Code Tabulation Area forecasts. ZCTA is 5-digit, ZIP3 is 3-digit regional.

    Input
    5-digit ZCTA or zip3
    Endpoint
    /api/v1/forecast/zcta or /api/v1/forecast/zip3

    Best for: Quick regional market checks, broad geographic summaries, fallback coverage.

    County forecast

    County-level forecast for market-wide analysis.

    Input
    5-digit county FIPS
    Endpoint
    /api/v1/forecast/county

    Best for: Market analysis, regional trends, fallback when local data is unavailable.

    State forecast

    State-level forecast for macro comparisons.

    Input
    2-digit state FIPS
    Endpoint
    /api/v1/forecast/state

    Best for: Statewide market trends, macro analysis.

    Hex (legacy)

    Compatibility endpoint for existing integrations. Not recommended for new integrations.

    Input
    H3 cell ID
    Endpoint
    /api/v1/forecast/hex

    Best for: Existing integrations only; prefer tract or tabblock for new work.

    Data coverage

    Parcel data

    Varies by jurisdiction. Check coverage by region to see where parcel-level data is available.

    Open interactive coverage atlas →

    Tract data

    Available nationwide. Most reliable for broad geographic queries and fallback when parcel data is unavailable.

    Tract REST reference →

    ZCTA/ZIP data

    Available nationwide. Best for quick regional market checks and broad geographic summaries.

    ZCTA REST reference →

    Common use cases

    Building a property tool

    Start with address or parcel data. Fall back to tract if parcel isn't available.

    Examples: Real estate apps, valuation tools, investment platforms

    Market analysis

    Use tract, county, or state endpoints for trends and comparisons.

    Examples: Market research, portfolio analysis, geographic summaries

    Map visualization

    Use tabblock for granular maps, or tract for neighborhood-level analysis.

    Examples: Interactive forecasts maps, geographic visualizations

    Monitoring your requests

    API Health

    Real-time health of all endpoints and data sources.

    View status dashboard →

    Data Freshness

    Forecasts refresh weekly (Tuesdays ~2 AM UTC). Each response includes as_of_date showing the data snapshot age.

    See response format →

    Coverage Availability

    Parcel data varies by jurisdiction. Use the coverage atlas to inspect source geographies, panel links, and public reference boundaries before choosing an endpoint.

    Open coverage atlas →

    Developer docs Full API referenceData catalog

    Documentation

    Start with the job you need to do, then move into the complete interface reference.

    Start and build

    Choose a task before choosing a protocol.

    Start HereForecastsData CatalogBenchmarks

    Interfaces

    REST, MCP, and typed client references.

    REST QuickstartFull API ReferenceMCP ToolsTypeScript SDKPython SDK

    Trust and operations

    Contracts, methodology, and live health.

    Schema ReferenceStatusMethodology