Arizona
LIHTC Year 15 and compliance-period data in Arizona
147 dated Arizona records, read from filed public sources rather than modelled, and callable by an AI agent with no key.
Short answer
Which LIHTC properties are reaching the end of a compliance period? In Arizona, 41 records are dated ahead of today. Every one of them is listed below in full, and they are free. 147 have been published in Arizona in total, counting those already past.
All 41 in Arizona
That is the whole Arizona population for this family, not a sample. The call underneath returns the same rows, up to its own fifty-row ceiling.
| Date | Property | City | Units | Amount | Source |
|---|---|---|---|---|---|
| 2026-12-31 | 50 E MAIN STRESIDENCES AT CENTER STREET STATION, MESA, AZ: placed in service in 2012, so the fifteen year compliance period ends in 2026, this year. 34 units. | MESA | 34 | — | hud_lihtc |
| 2026-12-31 | 4204 N NINTH STMADISON POINT, PHOENIX, AZ: placed in service in 2012, so the fifteen year compliance period ends in 2026, this year. 60 units. | PHOENIX | 60 | — | hud_lihtc |
| 2026-12-31 | SCATTERED SITESPASCUA YAQUI HOMES II, TUCSON, AZ: placed in service in 2012, so the fifteen year compliance period ends in 2026, this year. 56 units. | TUCSON | 56 | — | hud_lihtc |
| 2026-12-31 | 1351 N PINECLIFF DRFLAGSTAFF SENIOR MEADOWS, FLAGSTAFF, AZ: placed in service in 2012, so the fifteen year compliance period ends in 2026, this year. 60 units. | FLAGSTAFF | 60 | — | hud_lihtc |
| 2026-12-31 | 3140 KEARSAGE DRLAKEVIEW VILLAS, LAKE HAVASU CITY, AZ: placed in service in 2012, so the fifteen year compliance period ends in 2026, this year. 84 units. | LAKE HAVASU CITY | 84 | — | hud_lihtc |
| 2026-12-31 | TUNLII SUBDIVISIONYAVAPAI-APACHE NATION #4, CAMP VERDE, AZ: placed in service in 2012, so the fifteen year compliance period ends in 2026, this year. 35 units. | CAMP VERDE | 35 | — | hud_lihtc |
| 2026-12-31 | 304 S CLARK RDPINEVIEW MANOR, PAYSON, AZ: placed in service in 2012, so the fifteen year compliance period ends in 2026, this year. 49 units. | PAYSON | 49 | — | hud_lihtc |
| 2026-12-31 | 4141 N NINTH STENCANTO POINTE, PHOENIX, AZ: placed in service in 2012, so the fifteen year compliance period ends in 2026, this year. 54 units. | PHOENIX | 54 | — | hud_lihtc |
| 2026-12-31 | 5311 W TOROKO VAMPOPASCUA YAQUI HOMES I, TUCSON, AZ: placed in service in 2012, so the fifteen year compliance period ends in 2026, this year. 40 units. | TUCSON | 40 | — | hud_lihtc |
| 2026-12-31 | 125 S LINDA AVESENTINEL PLAZA, TUCSON, AZ: placed in service in 2012, so the fifteen year compliance period ends in 2026, this year. 143 units. | TUCSON | 143 | — | hud_lihtc |
| 2026-12-31 | 6280 S CAMPBELL AVETRINITY PLACE, TUCSON, AZ: placed in service in 2012, so the fifteen year compliance period ends in 2026, this year. 88 units. | TUCSON | 88 | — | hud_lihtc |
| 2026-12-31 | 1640 W ROESER RDGRANDFAMILIES PLACE OF PHOENIX, PHOENIX, AZ: placed in service in 2012, so the fifteen year compliance period ends in 2026, this year. 56 units. | PHOENIX | 56 | — | hud_lihtc |
| 2026-12-31 | 809 N FIFTH AVELOFTS AT MCKINLEY, PHOENIX, AZ: placed in service in 2012, so the fifteen year compliance period ends in 2026, this year. 60 units. | PHOENIX | 60 | — | hud_lihtc |
| 2026-12-31 | 1020 S CARMICHAEL AVECASA DEL SOL, SIERRA VISTA, AZ: placed in service in 2012, so the fifteen year compliance period ends in 2026, this year. 88 units. | SIERRA VISTA | 88 | — | hud_lihtc |
| 2026-12-31 | 675 N 16TH STAEROTERRA SENIOR VILLAGE, PHOENIX, AZ: placed in service in 2012, so the fifteen year compliance period ends in 2026, this year. 60 units. | PHOENIX | 60 | — | hud_lihtc |
| 2027-12-31 | 912 W HIGHLAND AVEHIGHLAND METRO APTS, PHOENIX, AZ: placed in service in 2013, so the fifteen year compliance period ends in 2027, 1 year from now. 62 units. | PHOENIX | 62 | — | hud_lihtc |
| 2027-12-31 | 1040 N NINTH STHERITAGE GLEN RETIREMENT APTS, COOLIDGE, AZ: placed in service in 2013, so the fifteen year compliance period ends in 2027, 1 year from now. 28 units. | COOLIDGE | 28 | — | hud_lihtc |
| 2027-12-31 | 1110 N 16TH STGARFIELD SACRED HEART HOUSING, PHOENIX, AZ: placed in service in 2013, so the fifteen year compliance period ends in 2027, 1 year from now. 100 units. | PHOENIX | 100 | — | hud_lihtc |
| 2027-12-31 | 84 TUFA STONESAN CARLOS HOMES VI, SAN CARLOS, AZ: placed in service in 2013, so the fifteen year compliance period ends in 2027, 1 year from now. 41 units. | SAN CARLOS | 41 | — | hud_lihtc |
| 2027-12-31 | 1980 W 30TH STLA POSADA APTS - SELLS, YUMA, AZ: placed in service in 2013, so the fifteen year compliance period ends in 2027, 1 year from now. 64 units. | YUMA | 64 | — | hud_lihtc |
| 2027-12-31 | 316 N AVE AKACHINA APTS, CASA GRANDE, AZ: placed in service in 2013, so the fifteen year compliance period ends in 2027, 1 year from now. 96 units. | CASA GRANDE | 96 | — | hud_lihtc |
| 2027-12-31 | 250 W HIGH COUNTRY TRAILHIGH COUNTRY ESTATES, FLAGSTAFF, AZ: placed in service in 2013, so the fifteen year compliance period ends in 2027, 1 year from now. 44 units. | FLAGSTAFF | 44 | — | hud_lihtc |
| 2027-12-31 | 12238 N 113TH AVEAURORA VILLAGE, YOUNGTOWN, AZ: placed in service in 2013, so the fifteen year compliance period ends in 2027, 1 year from now. 65 units. | YOUNGTOWN | 65 | — | hud_lihtc |
| 2027-12-31 | 1325 N 14TH STSTEPPING STONE PLACE, PHOENIX, AZ: placed in service in 2013, so the fifteen year compliance period ends in 2027, 1 year from now. 83 units. | PHOENIX | 83 | — | hud_lihtc |
| 2027-12-31 | 125 E UNIVERSITY DRESCOBEDO AT VERDE VISTA, MESA, AZ: placed in service in 2013, so the fifteen year compliance period ends in 2027, 1 year from now. 70 units. | MESA | 70 | — | hud_lihtc |
| 2027-12-31 | 802 N 30TH STCITY PLACE, PHOENIX, AZ: placed in service in 2013, so the fifteen year compliance period ends in 2027, 1 year from now. 134 units. | PHOENIX | 134 | — | hud_lihtc |
| 2027-12-31 | 1520 E APACHE BLVDGRACIE'S VILLAGE, TEMPE, AZ: placed in service in 2013, so the fifteen year compliance period ends in 2027, 1 year from now. 50 units. | TEMPE | 50 | — | hud_lihtc |
| 2027-12-31 | 324 S HORNETEMPLE SQUARE TOWNHOMES, MESA, AZ: placed in service in 2013, so the fifteen year compliance period ends in 2027, 1 year from now. 152 units. | MESA | 152 | — | hud_lihtc |
| 2027-12-31 | OSAY BO-OHPASCUA YAQUI HOMES IV, TUCSON, AZ: placed in service in 2013, so the fifteen year compliance period ends in 2027, 1 year from now. 40 units. | TUCSON | 40 | — | hud_lihtc |
| 2027-12-31 | 50 E MAIN STENCORE ON 1ST, MESA, AZ: placed in service in 2013, so the fifteen year compliance period ends in 2027, 1 year from now. 81 units. | MESA | 81 | — | hud_lihtc |
| 2027-12-31 | 808 E MISSOURI AVEMADISON GARDENS SENIOR COMMUNITY, PHOENIX, AZ: placed in service in 2013, so the fifteen year compliance period ends in 2027, 1 year from now. 133 units. | PHOENIX | 133 | — | hud_lihtc |
| 2027-12-31 | 1170 N IDAHO RDAPACHE JUNCTION TOWNHOMES, APACHE JUNCTION, AZ: placed in service in 2013, so the fifteen year compliance period ends in 2027, 1 year from now. 88 units. | APACHE JUNCTION | 88 | — | hud_lihtc |
| 2027-12-31 | 780 E CALLE MARIACHISUNNYSIDE POINTE VILLAS, TUCSON, AZ: placed in service in 2013, so the fifteen year compliance period ends in 2027, 1 year from now. 90 units. | TUCSON | 90 | — | hud_lihtc |
| 2027-12-31 | 650 N SECOND AVEUL2 (URBAN LIVING ON 2ND AVE), PHOENIX, AZ: placed in service in 2013, so the fifteen year compliance period ends in 2027, 1 year from now. 70 units. | PHOENIX | 70 | — | hud_lihtc |
| 2027-12-31 | 620 N SECOND AVEMARQUEE, PHOENIX, AZ: placed in service in 2013, so the fifteen year compliance period ends in 2027, 1 year from now. 34 units. | PHOENIX | 34 | — | hud_lihtc |
| 2027-12-31 | 2254 W MAIN STLA MESITA, MESA, AZ: placed in service in 2013, so the fifteen year compliance period ends in 2027, 1 year from now. 80 units. | MESA | 80 | — | hud_lihtc |
| 2027-12-31 | 2247 E VAN BUREN STTHE LOFTS @ 10, PHOENIX, AZ: placed in service in 2013, so the fifteen year compliance period ends in 2027, 1 year from now. 78 units. | PHOENIX | 78 | — | hud_lihtc |
| 2027-12-31 | 1604 W PASADENA AVEVILLAS AT PASADENA, PHOENIX, AZ: placed in service in 2013, so the fifteen year compliance period ends in 2027, 1 year from now. 34 units. | PHOENIX | 34 | — | hud_lihtc |
| 2027-12-31 | 1555 E WASHINGTON STWASHINGTON POINTE APTS, PHOENIX, AZ: placed in service in 2013, so the fifteen year compliance period ends in 2027, 1 year from now. 54 units. | PHOENIX | 54 | — | hud_lihtc |
| 2027-12-31 | 15 RISING SUN DRSAN CARLOS HOMES V, BYLAS, AZ: placed in service in 2013, so the fifteen year compliance period ends in 2027, 1 year from now. 40 units. | BYLAS | 40 | — | hud_lihtc |
| 2027-12-31 | 305 W PIMA STMARCOS DE NIZA, PHOENIX, AZ: placed in service in 2013, so the fifteen year compliance period ends in 2027, 1 year from now. 374 units. | PHOENIX | 374 | — | hud_lihtc |
Read from the published event tape on 2026-09-12.
The call that returns this
One anonymous POST. No key, no signup, no rate card. Raise limit to 50, or change state to any of the 56 covered.
curl -s https://exchange-production-9123.up.railway.app/mcp \
-H 'Content-Type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"search_property_events","arguments":{"event_type":"COMPLIANCE_PERIOD_ENDING","state":"AZ","within_days":1825,"limit":500}}}'Putting this in your own agent
The same endpoint is a Model Context Protocol server, so an assistant can ask it the question instead of you reading a table. It answers for every covered state, not just Arizona, and it is the same free tier.
Claude Code
one command, then it is available in every session
claude mcp add --transport http dfx-real-estate https://exchange-production-9123.up.railway.app/mcp
Claude Desktop
claude_desktop_config.json, then restart the app. It cannot reach a remote server directly, so this bridges through mcp-remote.
{
"mcpServers": {
"dfx-real-estate": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://exchange-production-9123.up.railway.app/mcp"
]
}
}
}Cursor, Windsurf, Cline and Zed
the mcp.json their settings panel writes
{
"mcpServers": {
"dfx-real-estate": {
"url": "https://exchange-production-9123.up.railway.app/mcp"
}
}
}VS Code
the servers key, which is spelled differently to everything above
{
"servers": {
"dfx-real-estate": {
"type": "http",
"url": "https://exchange-production-9123.up.railway.app/mcp"
}
}
}Then ask it this
Nothing names DFX. If the install worked, the assistant picks the tool itself.
Which LIHTC properties in Arizona reach Year 15 in the next three years?
There is no signup, no API key and no OAuth for anything free, and eleven of the twelve tools are free. A plain GET on the endpoint returns every tool schema, so a client can be pointed at it and evaluated before it is trusted.
Where this does not help
Compliance periods are statutory and every one falls on 31 December, so a count bucketed by day shows a December cliff that is an artefact of the statute rather than a market event.
The same question in other states
- Alabama 158
- Alaska 39
- American Samoa 113
- Arkansas 188
- California 1,406
- Colorado 150
- Connecticut 70
- Delaware 43
- District of Columbia 94
- Florida 364
- Georgia 361
- Guam 5
- Hawaii 37
- Idaho 75
- Illinois 319
- Indiana 268
- Iowa 183
- Kansas 156
- Kentucky 222
- Louisiana 360
- Maine 77
- Maryland 199
- Massachusetts 191
- Michigan 405
- Minnesota 232
- Mississippi 184
- Missouri 296
- Montana 55
- Nebraska 120
- Nevada 84
- New Hampshire 69
- New Jersey 283
- New Mexico 30
- New York 1,057
- North Carolina 353
- North Dakota 63
- Northern Mariana Islands 1
- Ohio 469
- Oklahoma 139
- Oregon 187
- Pennsylvania 266
- Puerto Rico 89
- Rhode Island 64
- South Carolina 226
- South Dakota 67
- Tennessee 234
- Texas 470
- US Virgin Islands 9
- Utah 103
- Vermont 95
- Virginia 338
- Washington 334
- West Virginia 82
- Wisconsin 286
- Wyoming 41
Facts on this page were last checked against the running product on . Prices are read from the live billing configuration, so this page and your invoice cannot disagree. The machine-readable version of this record is at /ai/entity.json.