HomFax SIU™ · Institutional access

Verify the claim against what the sky did.

HomFax SIU is a standalone fraud-investigation platform for carrier Special Investigation Units, third-party administrators, regulators and law enforcement. It checks a property claim against radar ground truth at that parcel on the claimed date, against the HomFax property baseline, and against the telemetry of every photograph submitted — then hands the investigating authority a sealed, Bates-numbered evidence packet. The engine flags and explains. The authority determines.

RADAR GROUND TRUTH · 3 KM PER ROOF SHA-256 CHAIN OF CUSTODY ENGINE EXPLAINS · AUTHORITY DETERMINES PATENT PENDING · US 19/417,288 · US 64/027,247

Verification — live example, Arlington TX

!
Temporal discrepancy
Claimed loss date 2026-01-20 had 0.0" hail at the parcel. Closest qualifying event: 2026-04-26 (1.50" hail), 96 days after the claimed date.
!
Forensic archives do not corroborate
AMHIS verification for 2026-01-20: NO_EVIDENCE (P = 0.029) across NCEI SWDI, NWS warnings and ERA5.
Field capture custody verified
Photo hashed at ingest, client hash matches, 12 m from the parcel
sha256: a591a6d4…9ad9f146e
?
Flagged for SIU · referral priority 84
Question posed: the claimed date of loss is 2026-01-20; the nearest qualifying event at this parcel was 2026-04-26. Which event is the claim for, and what evidence fixes the date?
What It Does

Three sources of truth. One reproducible answer.

Every verification is stored whole — the storm history used, the property facts used, the captures examined — and sealed with a hash of its inputs, so any flag can be reproduced years later from exactly what the engine saw.

1

Verify

StormCast™ supplies per-roof radar hail signatures and ground reports within 3 km, plus the AMHIS forensic date-of-loss verdict. HomFax™ supplies the baseline: roof age and size, prior claims, and whether the property record's hash chain still verifies. Field captures arrive with GPS, heading, device identity, timestamps and a client-side hash the server reconciles against the bytes it received.

2

Explain

Seventeen indicators, each with a severity, the evidence behind it, and — where the finding is adverse — the question the claim must answer. A saturating 0–100 referral-priority score and a verdict: verified consistent, review recommended, flagged for SIU, or insufficient data. Missing data is a stated gap, never an adverse finding.

3

Refer

A Bates-numbered referral packet — property baseline, engine run, indicators, captures with hashes, storm events, canvass outcomes, the audit trail — sealed with SHA-256 and re-verifiable by the recipient. The authority's determination, or its documented silence, is recorded as claim history. The engine cannot conclude that fraud occurred.

The Verification Engines

Built for the frauds that actually happen in roofing claims.

Date-shopping after a storm that missed the house. Canvass rings that file thirty claims where the sky did nothing. Damage on the sheltered side of the roof. Photographs taken before the loss. Each has a named, explainable check.

Spatial-temporal cross-verification

The claimed date of loss against what fell at that parcel: hail size, wind speed, tornado signatures, the nearest qualifying event in either direction, and the AMHIS forensic verdict from federal archives.

TEMPORAL_DISCREPANCY · SUB_THRESHOLD_EVENT · FORENSIC_NOT_CONFIRMED

Contractor Anomaly Index

A deterministic index of a contractor's or public adjuster's book against verified hail footprints — with same-date and reporting-lag terms that separate a real storm from a canvass wave. Every term is recomputable from the claims it cites.

CONTRACTOR_RING_ALERT · PA_RING_ALERT · CAI ≥ 85

Directional impact vs storm vector

Roof slopes classified as windward, cross or sheltered against the storm's motion. Damage confined to sheltered slopes while exposed slopes are clean becomes a question the claim must answer.

VECTOR_MISMATCH · VECTOR_MIXED · VECTOR_ALIGNED

Evidence custody

Photographs hashed on arrival and reconciled with the client's hash; capture GPS measured against the parcel; capture and EXIF timestamps against the claimed date; hardware attestation recorded. Nothing is overwritten.

PHOTO_PREDATES_DOL · CAPTURE_OFFSITE · HASH_MISMATCH
Who It's For

Institutional access, provisioned by name.

There is no public sign-up and no app-store build. Every account belongs to a named individual in a verified organization, holds one role, and is audited on every read and write of the investigative record.

Carrier SIU & TPA

Triage the queue by evidence, not hunch

  • One-call verification from your claim system — POST /api/v1/siu/verify-claim
  • Referral priority, temporal variance and the Contractor Anomaly Index on every claim
  • Investigator, supervisor and field-agent roles; carrier liaisons record determinations
  • Sealed packets ready for Chapter 701 good-faith reporting
Request Carrier Access
Regulators & NICB

Receive referrals you can verify

  • Every packet re-verifies against its own SHA-256 seal
  • Bates-numbered exhibits cite the storm record, the capture hash, the run
  • The determination you issue — or your silence — becomes the record
  • Read-only auditor role for oversight
Request Regulator Access
Law Enforcement & Prosecutors

Evidence that explains itself

  • Radar and federal-archive ground truth, not opinion
  • Chain of custody explicit on every photograph
  • Party records carry a written predicate and a review date
  • No person is scored; the claim is the unit of analysis
Request Agency Access
Posture

The engine flags and explains. A human authority determines.

HomFax SIU never issues a fraud finding. It documents what the evidence is consistent with, what it is not consistent with, and the question the claim must answer.

That posture is enforced in the software, not in a policy: the confirmed-fraud state is unreachable from the engine and from any status control. It exists only as a recorded determination attributed to a carrier SIU, the Texas Department of Insurance, NICB, or law enforcement.

  • Texas Insurance Code Chapter 701. Packets are built as the good-faith report the chapter contemplates — evidence, indicators, questions, determination.
  • No automated adverse action. Outputs are referral priorities; coverage and payment decisions stay with the carrier, outside the system.
  • No protected-class inputs. Nothing in the data model reads race, national origin, religion, sex, familial status, disability or income.
  • Party records carry a predicate. A contractor or adjuster enters the system only with a written basis and a review date; retirement is a status, not a deletion.
  • Missing data is a gap, not a flag. If StormCast cannot be reached, the verdict is INSUFFICIENT_DATA.
Access

Request institutional access.

Tell us who you are and in what capacity you investigate. HomFax administration verifies the organization, provisions named accounts with the right role, and — for carrier claim systems — issues a scoped integration key. Nothing is created automatically.

Access request

Accounts are provisioned to named individuals only. We reply from homfaxtm@homfaxtm.com.

How provisioning works

  1. We verify the organization and your capacity within it.
  2. An administrator creates your account in HomFax SIU with one role: investigator, supervisor, field agent, carrier liaison, or auditor.
  3. You sign in at homfaxtm.com/siu, set your own password, and every action from then on is in the audit log.
  4. Carrier claim systems receive a scoped, revocable integration key bound to the carrier.

Carrier integration — one call

Submit the claim, the parcel and the field intake; receive the verdict, the score, the reasons and the evidence-vault status.

POST /api/v1/siu/verify-claim x-api-key: ••• { "claim_id": "…", "parcel_id": "TX-TARRANT-…", "claimed_loss_date": "2026-04-15", "contractor_id": "…", "field_intake": { "image_payload_base64": "…", "gps_coords": { "lat": 32.7555, "lng": -97.3308 }, "capture_timestamp": "…", "client_sha256": "…" } } → { "verdict": "FLAGGED_FOR_SIU", "anomaly_score": 91, "temporal_variance_days": 37, "flag_reasons": [ "TEMPORAL_DISCREPANCY: …", "VECTOR_MISMATCH: …", "CONTRACTOR_RING_ALERT: …" ], "evidence_vault": { "sha256_hash": "…", "chain_of_custody_status": "VERIFIED_UNALTERED" } }

Part of the HomFax™ system.

The same property record that proves a legitimate claim is the record that exposes a false one.

Request Access Authority Sign In