Bricked API vs HouseCanary
HouseCanary models the value. Bricked builds the offer.
| Bricked API | HouseCanary | |
|---|---|---|
| Built for | Underwriting | Valuations & analytics |
| One call returns | A finished underwrite | AVMs & analytics |
| Comps in the response | You pick them | |
| Appraiser-style adjustments | From your comp picks | |
| Photo condition scoring | Scenario-based | |
| Itemized repair estimates | ||
| ARV & offer price | AVM & ranges | |
| Non-disclosure coverage | Modeled | |
| Shareable report link |
In practice
HouseCanary is at the institutional end of valuation APIs, and for portfolio marks and lending models it belongs there. Acquisition teams need something different from a value opinion. They need the offer math, and that is what the Bricked API returns.
The HouseCanary AVM tells you what the model believes. Bricked shows you the comps, the condition scores, and the adjustments behind the number.
HouseCanary adjusted values require your analyst to pick the comps. Bricked picks and adjusts them automatically, with the same method an appraiser uses.
In HouseCanary, condition is a scenario input instead of an observation. In Bricked, condition is read from the listing photos of every comp.
No HouseCanary endpoint includes a repair budget. An itemized repair estimate is included in every Bricked response.
What a response includes
POST an address, poll the property, and read the underwrite. The full reference is at docs.bricked.ai.
property Normalized details for the subject address
comps Selected comparables, condition-scored and adjusted
cmv As-is market value
arv After-repair value
repairs Itemized line items with costs, plus the total
shareLink A client-ready report anyone can open
“We've cut our underwriting time by 70%. The team actually enjoys doing comps now.”
Kwame, Acquisitions Manager
Put underwriting in your pipeline
Generate an API key from your dashboard and make your first call in minutes.