Choose one core source
Start with RentCast. Compare it with Realie. Keep ATTOM as the enterprise benchmark if one contract could replace several vendors.
The short version
Three buying decisions, not six subscriptions
RentCast, Realie, and ATTOM overlap as core property sources. Shovels, HazardHub, and Regrid add different layers.
Add the intelligence layers
Shovels adds renovation and permit history. HazardHub adds property-level peril scores. Neither replaces the core record.
Buy maps only when needed
Regrid becomes useful when parcel boundaries, footprints, or an interactive map are part of the next product slice.
Monthly planning view
Estimated cost by home volume
Public self-service prices are shown exactly. Sales-led products use clearly labeled planning allowances.
Swipe the table to compare every volume and confidence label.
| Provider | 250 homes | 500 homes | 1,000 homes | Pricing confidence |
|---|---|---|---|---|
| 1. RentCast | $40 | $74 | $74 | Official public |
| 2. Realie | $33.75 | $50 | $50 | Calculated from public rates |
| 3. ATTOM | $500–$1,500 | $500–$1,500 | $500–$1,500 | Planning allowance |
| 4. Shovels | $599–$700 | $599–$700 | $599–$700 | Starting price plus buffer |
| 5. HazardHub | $625–$2,750 | $750–$3,500 | $1,000–$5,000 | Planning allowance |
| 6. Regrid Standard | $375 | $375 | $375 | Optional, official public |
How to read this: RentCast assumes one successful property-record request per home. Realie assumes one token per home. Shovels cost depends on the number of permit records returned. HazardHub assumes one bundled risk lookup per home. Regrid Standard includes 2,000 parcel records and 200,000 map tiles per month.
Provider details
What each service would do for HFHS
Each option is placed by its likely role in Home Intelligence, not by the size of its marketing catalog.
RentCast
Core property records, value, rent, and market data
What it is
A self-service property API covering structural facts, tax and sale history, ownership signals, automated values, rent estimates, listings, and market data.
What HFHS would use it for
Turn an address into a starting home profile. Pull age, size, property type, assessed value, sale history, and an estimated value before the first conversation or visit.
Why it is different
It combines useful national property coverage with simple public pricing and a low entry cost. That makes it the easiest core adapter to test without an enterprise contract.
Watch-outs
A property record, value estimate, rent estimate, and market lookup can be separate requests. Cache and display rights still need contract review before production use.
Realie
Alternate property record source with a deeper raw schema
What it is
A token-priced API for property, assessor, deed, mortgage, tax, lot, owner, and valuation data. Its schema exposes many source fields rather than only a short summary.
What HFHS would use it for
Compare coverage and field quality against RentCast. It could fill gaps in ownership, mortgage, lot, deed, or tax history and give the team a second source when facts conflict.
Why it is different
The public tiers are inexpensive and the record model is deep. That makes it attractive for a controlled bake-off and for provenance-aware comparisons between sources.
Watch-outs
We need written confirmation of token debit rules, consumer display rights, persistence rights, and feature equivalence. Low usage price does not automatically include every premium dataset.
ATTOM
Enterprise property-data benchmark and possible consolidation vendor
What it is
A large enterprise property-data platform covering ownership, tax, deed, mortgage, valuation, listings, neighborhood, parcel, climate, hazard, and building information.
What HFHS would use it for
Evaluate whether one broad contract can supply the core home record and enough enrichment to reduce the number of separate vendors HFHS has to manage.
Why it is different
Its strength is breadth, established national coverage, and enterprise packaging. It is the benchmark for judging whether cheaper self-service sources are good enough.
Watch-outs
ATTOM does not publish production API tiers. Endpoint families, retention, display rights, annual commitments, and add-on datasets can all change the quote.
Shovels
Permit, contractor, renovation, and component-history intelligence
What it is
A normalized building-permit API that organizes permits, contractors, inspections, job types, dates, and project values across local jurisdictions.
What HFHS would use it for
Find evidence of roof, HVAC, plumbing, electrical, solar, addition, and renovation work. Permit dates can help estimate system age and guide the first inspection.
Why it is different
Core property APIs describe the home as recorded today. Shovels helps explain what changed, when it changed, who did the work, and which systems may be nearing their next service cycle.
Watch-outs
Paid usage is tied to records returned, not just address searches. One older home may return many permits. Coverage and detail also vary by jurisdiction.
Guidewire HazardHub
Property-level peril scores and insurance-grade risk attributes
What it is
A property-risk API with more than 50 peril scores in one lookup and a catalog of over 1,200 risk factors. Coverage includes flood, wildfire, wind, hail, earthquake, lightning, crime, and more.
What HFHS would use it for
Add location-specific risks to the home record. The product could turn those risks into inspection priorities, seasonal reminders, prevention advice, and homeowner education.
Why it is different
It packages many hazards at the property level through one commercial source. That is more operationally useful than stitching together broad public maps that use different scales and definitions.
Watch-outs
Guidewire does not publish a production rate card. Pricing depends on volume, selected data elements, permitted use, display rights, and minimum commitments.
Regrid
Optional parcel boundaries, identifiers, geometry, and map tiles
What it is
A national parcel-data and mapping platform that provides parcel IDs, boundaries, geometry, ownership fields, address data, and rendered map tiles.
What HFHS would use it for
Show the exact parcel on a map, support boundary-aware property views, match records to a parcel ID, and power map interactions around a home.
Why it is different
Its primary value is spatial. It is the only provider in this shortlist centered on parcel geometry and map delivery rather than facts, permits, or hazards.
Watch-outs
It is unnecessary for the first non-map Home Intelligence slice. Storage, derivative use, termination, and AI-related rights need careful contract review before parcel data is persisted.
Working budget
What a likely launch stack costs
This models RentCast as the core source, Shovels for permits, and HazardHub for risk. It does not add Realie and ATTOM on top.
Without parcel maps
RentCast + Shovels + HazardHub
250 homes$1,264–$3,490
500 homes$1,423–$4,274
1,000 homes$1,673–$5,774
With Regrid parcel maps
Recommended stack + Regrid Standard
250 homes$1,639–$3,865
500 homes$1,798–$4,649
1,000 homes$2,048–$6,149
Recommended sequence
Spend in stages
Prove field quality and product value before committing to the expensive enrichment contracts.
Build the first core adapter and test real field coverage for $40 to $74 per month.
Measure match rate, schema depth, freshness, and conflicts on the same controlled home sample.
Use the 250-request Shovels trial. Ask HazardHub and ATTOM for written proposals and rights terms.
Add the $375 map plan only when parcel boundaries or map interactions enter the approved slice.