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 sits 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 AVM tells you what the model believes. Bricked shows you the comps, the condition scores, and the adjustments behind the number.
Adjusted values require your analyst to pick the comps. Bricked picks and adjusts them automatically, the way an appraiser would.
Condition is a scenario input, not an observation. Condition is read from the listing photos of every comp.
No repair budget in any endpoint. An itemized repair estimate ships in every response.
What a response includes
POST an address, poll the property, read the underwrite. Full reference 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.