F5380 phase-2 enrichment source catalog. Every entry was live-probed from apps-box on 2026-09-29 (see probe_note/probed_utc). status is one of: ok (reachable, real data confirmed), needs_registration (reachable, requires a free API key/token this fork did not request), blocked_network (this box could not reach the host at probe time -- DNS/connection failure, not necessarily a dead source), needs_dataset_discovery (portal reachable but this fork did not verify a real working dataset id). Nothing here is loaded unless status=ok AND a loader ran (see loaded_counties). Never treat a blocked_network entry as 'the source does not exist' -- re-probe from a box with broader egress before concluding that.
| Source id | Label | Type | Status | Counties loaded | Probed | Probe note |
|---|---|---|---|---|---|---|
arcgis_denver_co | Denver / Colorado open data (permits, code enforcement) | arcgis_query | needs_dataset_discovery | 0 | 2026-09-29T19:05:00Z | Host reachable (HTTP 400 on a bare /resource/ probe -- a real Socrata-family error page, not a connection failure), but this is the STATE of Colorado's portal, not Denver-city-specific, and no dataset id was verified. denver_co has 7,229 lead rows on file (3rd-largest county). Next step: find Denver's own open-data portal (denvergov.org/opendata) and a real dataset id. |
census_acs5 | Census Bureau ACS 5-Year Estimates | census_acs | needs_registration | 0 | 2026-09-29T19:00:00Z | Reachable; API returned an HTML 'Missing Key' error page for an unauthenticated query (confirms the endpoint is live but requires a key for county-level pulls). A free key is available with no cost at https://api.census.gov/data/key_signup.html -- request one and set CENSUS_API_KEY to activate this source. |
fema_nfhl | FEMA National Flood Hazard Layer (NFHL) | fema_arcgis | blocked_network | 0 | 2026-09-29T19:00:00Z | Both hazards.fema.gov and msc.fema.gov TLS-handshake-reset from apps-box at probe time (curl: 'Recv failure: Connection reset by peer' on hazards.fema.gov; 000/no-response on msc.fema.gov). This is a public, free, no-key ArcGIS REST service (identify-by-point query) -- the block is on THIS box's egress/TLS path, not a source restriction. Re-probe from a box with different egress before concluding FEMA itself refuses us. |
hud_fmr | HUD Fair Market Rents | hud_fmr_static | ok | 24 | 2026-09-29T19:00:00Z | RESOLVED 2026-09-29 by sibling fork F5379 (wh_tools.py rent_estimate()): the live token-gated API (HTTP 403 without a bearer token, see local_file below) was bypassed by pulling FMR figures from HUD's keyless public ArcGIS layer instead. Loaded for ALL 24 of our lead counties into a static local file -- no network call needed at request time. This module reads that file directly (see enrichment.hud_fmr_for_county()); do not re-fetch. |
hud_home_store | HUD Home Store / REO listings | hud_home_store | blocked_network | 0 | Not independently re-verified this pass. Per the F5124 earlier-work reference in this ticket's brief: no working free feed/API path was found for HUD Home Store listings as of that fork's work -- recorded as blocked per brief instruction ('HUD Home Store / REO feeds only if F5124's earlier work found a working path -- otherwise record as blocked'). Revisit only if F5124's own notes (search for F5124 in this repo's history/memory) surface a working endpoint. | |
socrata_cobb_ga | Cobb County GA open data | socrata_json | blocked_network | 0 | 2026-09-29T19:05:00Z | Connection failed (000, no response) from apps-box at probe time. cobb_ga has 2,317 lead rows on file. |
socrata_columbus_franklin_oh | Columbus / Franklin County OH open data | socrata_json | needs_dataset_discovery | 0 | 2026-09-29T19:05:00Z | Host reachable (HTTP 404 on a bare API-root probe -- a real response, not a connection failure), no dataset id verified. NOTE: our actual Ohio lead counties are cuyahoga_oh (4,134 rows) and clermont_oh (1,535 rows), NOT franklin_oh -- Columbus/Franklin was named in the brief but does not match our warehouse today. Cataloged as requested; a Cleveland/Cuyahoga County portal would be higher-value and was not probed this pass. |
socrata_dallas_permits | City of Dallas -- Building Permits (proof of concept) | socrata_json | ok | 0 | 2026-09-29T19:05:00Z | CONFIRMED WORKING -- fetched 2 real rows (permit_number, permit_type, issued_date, contractor, value, street_address, zip_code). This is a proof-of-concept load only: Dallas is NOT currently one of our lead-warehouse counties (we hold harris_tx, tarrant_tx, williamson_tx -- not dallas_tx), so no w_leads row can be joined to it yet by county. Cataloged and loadable the moment a Dallas County lead source is added. |
socrata_fortworth_permits | City of Fort Worth -- Building Permits / Code Compliance (Tarrant County seat) | socrata_json | needs_dataset_discovery | 0 | 2026-09-29T19:05:00Z | Portal host resolves and the ArcGIS-Hub-backed root responded, but the specific dataset id this fork guessed (vksd-fqxb) returned an 'ArcGIS Hub Unsupported' page, not data -- that id was a guess, not a verified dataset. Fort Worth is the seat of tarrant_tx, our LARGEST lead county (96,558 rows) -- highest-value target to fix next: browse https://data.fortworthtexas.gov/browse to find the real permits/code-compliance dataset id, then this becomes an 'ok' socrata_json source with zero code changes (the generic reader already handles it). |
socrata_lasvegas_clark_nv | Las Vegas / Clark County NV open data (permits, code enforcement) | socrata_json | blocked_network | 0 | 2026-09-29T19:05:00Z | Connection failed (000, no response) from apps-box at probe time. clark_nv is our 2nd-largest lead county (13,896 rows) -- high value once egress allows a re-probe. |
socrata_sarasota_fl | Sarasota County / City FL open data | socrata_json | blocked_network | 0 | 2026-09-29T19:05:00Z | Connection failed (000, no response) from apps-box at probe time. sarasota_fl has 232 lead rows on file. |
socrata_virginia_beach_fairfax | Virginia Beach / Fairfax County VA open data | socrata_json | blocked_network | 0 | 2026-09-29T19:05:00Z | Both hosts returned connection failures (000) from apps-box at probe time. Our actual VA lead counties are richmond_va (7,252 rows) and norfolk_va (3,491 rows), NOT Virginia Beach or Fairfax -- named in the brief but not a direct match; cataloged as requested. |
Entity: Elite AI Holdings LLC. Site index · Free vs. pro tools · Open data API · Correction / opt-out · Privacy · Terms · Do Not Sell / Privacy Request · Account.
← Elite AI Empire home