HUD Affordable Housing Explorer — LIHTC + Multifamily + Public Housing

One search across three HUD affordable-housing programs, returned as a single unified property record — with an Opportunity Zone flag computed for every property:

Program	Source layer (HUD eGIS, keyless)	What it covers
LIHTC	LIHTC/FeatureServer/0	40,500+ Low-Income Housing Tax Credit properties, ~2.6M units placed in service since 1987
HUD_INSURED	HUD_Insured_Multifamily_Properties/FeatureServer/0	FHA-insured multifamily properties (221(d)(4), 223(f), 232, 202/811...)
PUBLIC_HOUSING	Public_Housing_Developments/FeatureServer/0	Public housing developments with PHA contact + occupancy stats
Opportunity Zones	Opportunity_Zones/FeatureServer/13	Designated Qualified Opportunity Zone tract polygons (point-in-polygon flag)

No API key, no scraping-fragile HTML — this reads HUD's own ArcGIS services and normalizes every layer's incompatible schema (PROJECT vs PROPERTY_NAME_TEXT vs PROJECT_NAME, LI_UNITS vs TOTAL_ASSISTED_UNIT_COUNT vs ACC_UNITS...) into one clean shape you can filter, join, and map.

Who uses this

• LIHTC investors & syndicators — screen existing tax-credit stock by state/city/size, spot properties in Opportunity Zones for stacked incentives, and pull owner names for outreach.
• Affordable-housing developers — map the competitive landscape (what exists, how many low-income units, year placed in service) before siting a new deal.
• CRE lenders & brokers — build lead lists of HUD-insured multifamily and LIHTC properties with unit counts and management contacts.
• Housing researchers & journalists — cross-program inventory of subsidized housing in any state, with coordinates ready for GIS.
• AI agents — a chainable MCP tool that turns "affordable housing near X" questions into structured rows.

Example input

{
  "states": ["CO"],
  "programs": ["LIHTC", "HUD_INSURED", "PUBLIC_HOUSING"],
  "city": "Denver",
  "minUnits": 50,
  "includeOpportunityZoneFlag": true,
  "onlyOpportunityZone": false,
  "maxResults": 500
}

Output fields (one row per property)

• program — LIHTC | HUD_INSURED | PUBLIC_HOUSING
• source_id — stable HUD id (LIHTC HUD_ID, multifamily PROPERTY_ID, public-housing DEVELOPMENT_CODE)
• property_name, address, city, state, county, zip
• units_total — total units (null when HUD reports "not available")
• units_low_income — LIHTC low-income units / assisted units / ACC units
• year_placed_in_service — LIHTC year placed in service or multifamily occupancy year
• owner_or_manager — management agent (HUD-insured) or public housing authority. Null for LIHTC rows (HUD does not publish an owner/company in the LIHTC layer)
• program_detail — FHA program type, LIHTC allocation, or PHA code/status
• latitude, longitude — WGS84 coordinates (HUD enterprise geocode)
• opportunity_zone — true when the property sits inside a designated Qualified Opportunity Zone tract (computed locally by point-in-polygon; null if disabled)
• oz_tract_geoid — the OZ tract's 11-digit GEOID when flagged

Results are deduplicated within a run and priced per row (pay-per-event Result).

Use as an MCP tool

This actor is exposed via mcp.apify.com — AI agents (Claude, Cursor, custom agents) can call it as a tool. The input schema is fully described and the output rows are flat, typed, and field-documented, so an agent can chain it: e.g. find LIHTC properties in Opportunity Zones in Denver over 100 units, then look up their owners.

FAQ

How do I get a list of LIHTC properties by state? Set states to your state codes and programs to ["LIHTC"] — each row includes units, low-income units, year placed in service, allocation amount, and lat/lon. (HUD does not publish an owner/company in the LIHTC layer, so owner_or_manager is null for LIHTC rows; it is populated for HUD-insured and public-housing programs.)

How do I find affordable housing properties in Opportunity Zones? Set onlyOpportunityZone to true. The actor fetches the designated QOZ tract polygons for your states and keeps only properties whose coordinates fall inside one.

Which HUD database does the LIHTC data come from? HUD's national LIHTC database (the only complete national source on tax-credit project size, unit mix, and location), published through HUD's public ArcGIS services.

Can I filter HUD multifamily properties by size? Yes — minUnits filters on total units. Note some HUD-insured records (e.g. hospitals/nursing homes) report 0/unknown units and are dropped when a minimum is set.

Is public housing included? Yes — public housing developments with the operating housing authority as owner_or_manager. Year placed in service is not published for this layer.

Does it work for the whole US? Yes, any US state or territory code; query multiple states in one run. Data freshness follows HUD's own layer updates.

Where do the Opportunity Zone boundaries come from? HUD's Opportunity_Zones FeatureServer (designated QOZ tracts per IRC 1400Z-1). The flag is computed locally with ray-casting point-in-polygon — no paid geocoding APIs.