Terms on this page
Site-by-site retrieval matrix
| Site | Working method | Failure mode otherwise |
|---|---|---|
cilovelandco.civicweb.net | VPN + plain curl | — |
reflect-cityofloveland-co.cablecast.tv | VPN + plain curl | — |
loveland.legistar.com | n/a — empty tenant | “Invalid parameters!”; Loveland does not use Legistar |
projects.propublica.org/nonprofits/api/v2/ | VPN + plain curl | — |
projects.propublica.org/nonprofits/download-filing | (blocked) | Cloudflare security check on PDF downloads |
www.lovgov.org | VPN + curl_cffi popular browser UA | Akamai 403 on plain curl |
www.larimer.gov | VPN + curl_cffi popular browser UA | Bot manager requires browser TLS fingerprint |
maps1.larimer.org/arcgis | VPN + curl_cffi | — |
apps.larimer.org/api/assessor2/ | VPN + curl_cffi | — |
records.larimer.org/landmarkweb | VPN + curl_cffi, requires registered account for image fetch | placeholder PNG returned otherwise |
apps.dfi.wi.gov | VPN + curl_cffi + ASP.NET form scrape (viewstate) | — |
coloradosos.gov/biz | VPN + curl_cffi + Struts form POST | — |
www.loopnet.com | (blocked) | Full Akamai Bot Manager JS challenge — needs headless browser |
www.realtor.com | (rate-limited) | 429 from VPN exit; would need residential proxy |
API endpoints discovered
These are the non-obvious endpoints that produced most of the leverage:
- Larimer Recorder (Pioneer Landmark Web):
POST /LandmarkWeb/Search/SetDisclaimer· accept TOSPOST /LandmarkWeb/Search/QuickSearch· submit search criteriaPOST /LandmarkWeb/Search/GetSearchResults· DataTables JSON resultsPOST /LandmarkWeb/Document/Index· load doc into sessionGET /LandmarkWeb/Document/GetDocumentImage/?documentId=…&pageNum=…· image bytes
- Larimer Assessor:
GET /api/assessor2/?prop=detail&accountno=R…· full property detail JSONGET /api/assessor2/?prop=sales&accountno=R…· deed/sale history with reception #sGET /api/assessor2/treasurer/?prop=doc&receipts=…· document → grantor/grantee/legal lookupGET /api/assessor2/treasurer/?prop=propinfo&accountno=R…· assessed and actual values, all years
- Larimer GIS REST (parcel polygons + addresses):
- Cablecast video archive:
GET /cablecastapi/v1/shows/?channel=1&page_size=200&order=-event_dateGET /cablecastapi/v1/shows/{id}?include=vodsGET /cablecastapi/v1/vods/{id}→urlfield is the direct MP4GET /cablecastapi/v1/vods/{id}/chapters· WebVTT chapter markers
- ProPublica Nonprofit Explorer:
GET /nonprofits/api/v2/search.json?q=…&state[id]=COGET /nonprofits/api/v2/organizations/{EIN}.json
Tools used
curl_cffiwithimpersonate="popular browser UA"for any site that rejects plain curlBeautifulSoup4for HTML parsing of ASP.NET / Struts results pages- Hugo 0.131.0 extended for this static site
Reproducibility check
Any reader with similar tooling and a free Larimer Landmark Web registered
account can re-derive every documented number in this dossier. The two recorded
deeds (reception #s 20210116996 and 20210116998) and the assessor’s
?prop=detail and ?prop=propinfo responses are the
fixed points. The only number that depends on a non-deterministic methodology
is the assessor’s time-adjusted resale value ($2,686,365) — their
internal commercial-RE index.
Methodological note on the HoNS exclusion analysis
The argument in Chapter 11 that the
House of Neighborly Service (HoNS) absence from the
599 W 71st RFA candidate pool is structurally explained by the
Christopher M. Say overlap (HoNS Vice President + sitting Loveland
Planning Commissioner April 2025 → April 2026 + Klein-RA’d
2025 Ward 3 candidate + Class 4 felony aggravated-animal-cruelty
defendant by April 2026) is a parsimony argument, not a causal claim.
The dossier does not assert that HoNS was deliberately excluded; the load-bearing
verification target is the City Clerk’s December 2025 /
January 2026 RFA solicitation distribution list (CORA #5,
Chapter 09). Primary source for the Say profile
is tier1/say_profile/FINDINGS.md.
OSINT collection methodology
This dossier was assembled using open-source intelligence techniques. The methodology is disclosed here so any reader can reproduce or independently verify any cited claim.
- Direct retrieval of publicly-available primary records
- Larimer County Recorder Landmark Web; Colorado Secretary of State BizSearch; Wisconsin Department of Financial Institutions Corporate Search; Internal Revenue Service Tax Exempt Organization Search; ProPublica Nonprofit Explorer; Colorado SOS TRACER campaign-finance database; Federal Election Commission disclosures; City of Loveland CivicWeb agenda portal; City of Loveland OpenGov transparency portal; Larimer County Assessor public API. Every retrieval is reproducible by any reader from a standard browser at the cited URL.
- Web-scale archival
- The Internet Archive Wayback Machine and
archive.todaywere used to capture point-in-time snapshots of paywalled, ephemeral, or adversary-controlled URLs. Every URL footnote that has a Wayback snapshot at the time of capture carries the snapshot permalink alongside the original location; the local-file path is provided when a captured copy is preserved alongside the dossier. - Local content preservation
- Where targets used commercial bot-management (e.g. the City of
Loveland portal sits behind an Akamai bot-manager that blocks
unsigned automated retrieval; the Bridge House withdrawal news
release #8260 is the most prominent example) or had previously
deleted public content (one Scottsdale Progress article was confirmed
deleted between initial capture and publication), pages were rendered
locally with a Chrome 131 user-agent and matching TLS-fingerprint
profile via
curl_cffito obtain the content as it would render to a normal browser. Hash-preserved metadata (URL, retrieval timestamp, HTTP response headers, content SHA-256) is stored alongside the captured artifact at the local-file path cited in the footnote. - Egress
- Initial primary-record retrieval used the public host’s default egress through a commercial VPN endpoint (IVPN, Denver exit). This is disclosed so any reader can reproduce the retrievals by either using the same path or by replaying the cited URLs from a standard browser. The captured content does not depend on the egress path; the egress disclosure exists to enable reader replay and to neutralise any subsequent characterisation of the collection as concealed.
- What this methodology is not
- No social engineering, no unauthorized access, no impersonation, no credential theft. Every cited source is a public record retrieved from its primary source, a quoted news article with attribution, a quoted dais statement with timecode, a Form 990 filing with EIN, a recorded instrument with reception number, or a derived figure with arithmetic shown. The CFAA compliance posture is at /about/#cfaa-compliance.
- Reproducibility statement
- The point of disclosing the collection stack is reader independence: every captured snapshot is reproducible by a reader using either standard browser retrieval at the cited URL, Wayback Machine retrieval at the cited snapshot URL, or local-file inspection at the cited path. The collection technique is a workaround for adversary-aware edge blocking on a subset of targets, not a fact-laundering layer.
- License
- This dossier is published under Creative Commons CC-BY-SA-4.0; reproductions should keep the URL footnotes intact.