One address on a file, or a whole portfolio.

01 · Search

One address, while the file is open.

Type or paste an address. It resolves against the province’s own address and parcel sources, and both assessments come back for that point. An address that resolves ambiguously, or to a low-confidence match, stops for review rather than being guessed. an assessment attached to the wrong building is worse than no assessment.

02 · Portfolio

Batch and score a portfolio, with a report for every property.

Submit a book of properties, close the browser, and come back to it. Every property reaches a terminal state you can see: assessed, or stopped for review with the reason. Properties that were ambiguous, low-quality, unmatched or missing a verified parcel identifier are held for a person rather than resolved automatically.

The portfolio is processed in controlled batches. Neither the province’s address service nor the assessment engine gets to be overloaded when a large portfolio is submitted for scoring.

03 · API

Wire it into origination, renewal or review.

The same assessment as JSON. Every response carries its versions block, so a result stored in your system today resolves back to the method that produced it years from now. That is what makes a stored assessment auditable rather than a number of unknown provenance.

POST /v1/property/assess
{ "lat": 50.6745, "lon": -120.3273 }

→ fire   { assessment, composite: { formula, components[], … } }
  flood  { assessment }
  flood_score { composite, band, escalation, corroboration }
  forward_sortation_area
  versions { methodology_fingerprint, assessment_fingerprint }

Fire and flood arrive as independent complete results. No field combines them into a grade, and there is no field anywhere for a sum insured, a premium or a loss.

The forward sortation area travels with every assessment, so a book aggregates on the unit the federal climate return already uses without a second geocoding pass.