Home Value Estimate API - AVM, Rent, Forecast, Market

Turn a list of addresses into automated value estimates with their confidence range, rental estimates, characteristics, risk scores and the market conditions around them. Up to a hundred addresses per request.

This actor calls a residential property valuation and analytics API on your behalf and stores one row per property, geography or market reading. Bring your own key: paste your account key and secret into the input and the run uses your own plan and your own contract.

What you get

• A valuation with its uncertainty attached. The value estimate, its upper and lower bounds, and the forecast standard deviation, which is the model's own statement of how far off it expects to be. The same three for the rental estimate.
• 126 analytics components, mixed freely. Pick any combination in one run: value, rental value, characteristics, sales history, tax history, schools, flood, FEMA disaster areas, census, land value, mortgage liens, notices of default, owner occupancy, loan to value at origination and today, value forecasts, value within the block, and the postcode, block, metropolitan and state series that surround the property.
• Seven levels. An individual property, a census block, a census block group, a postcode, a metropolitan division, a metropolitan statistical area or a state. Components name their own level, and a component from the wrong one is refused before the first request rather than after it.
• Real batching. A hundred items per request, answered in the order they were sent, which is what makes a long address list affordable.
• Market pulse. Median days on market and its moving average, median list price and price per square foot, active and new listings, listings removed, the share with a price reduction, and months of supply, for sale or rental, as a snapshot or a time series.
• Per component outcomes. Every row records what each component returned rather than collapsing a partial answer into one verdict, so you can tell a property with no tax record from one the provider has never seen.
• Nothing thrown away. The curated columns sit at the top level for sorting and filtering; the whole result of every component rides along in components.

Pay per result

You are charged per record, never per request or per component, and only for rows that carry real data. An address the provider has nothing for is stored with the reason and costs nothing.

Event	Price	What it covers
Property record returned	$0.015	One property or geography with every component requested, valuation, rent and characteristics
Market reading returned	$0.006	One market pulse snapshot, or one period of a time series

Quick start

1. Get an API key and API secret from your provider account settings.
2. Paste them into API key and API secret. Both halves are required.
3. Leave Level on property, put one address in Items, and leave Components on value and details.
4. Set Maximum rows to the most you want to pay for.
5. Run it.

FAQ

What is an AVM?

An automated valuation model estimates a home's current market value from comparable sales, public records and property characteristics, without anybody visiting the property. This one returns the estimate together with an upper bound, a lower bound and a forecast standard deviation, so the row tells you how much to trust the number as well as what the number is.

What is the forecast standard deviation and why does it matter?

The forecast standard deviation, usually written FSD, is the model's expected error expressed as a fraction of the value. An FSD of 0.05 on a $325,000 estimate means the model expects to be within about five percent. The upper and lower bounds are derived from it. When a valuation is going into a lending, insurance or acquisition decision, the FSD is the field that decides whether the estimate is usable.

How do I write an address?

Three ways. An address followed by a postcode, such as 10216 N Willow Ave, 64157. An address followed by a city and a two letter state, such as 65239 Rosanne Prairie St, Bayardchester, CA. Or the provider's own readable slug, such as 65239-Rosanne-Prairie-Bayardchester-CA-90113. A line that names a street but no place is refused with an explanation, because the provider cannot place a street on its own and would answer it as an ordinary miss.

What is a component?

A component is one endpoint for one item: property/value for one address, zip/hpi_ts_forecast for one postcode. Components are how this API is organised and also how it is metered, so asking for four components across a hundred addresses counts as four hundred against the provider's rate limit even though it travels as one request. This actor logs that arithmetic before it starts.

Can I get a rental estimate as well as a sale value?

Yes. Add property/rental_value alongside property/value and both come back on the same row, each with their own bounds and forecast standard deviation. property/rental_value_forecast and property/rental_value_within_block add the forward view and the block comparison.

Can I check risk as well as value?

Yes. property/flood and property/fema_disaster_area cover flood, and the block hazard components cover earthquake, hail, hurricane, tornado and wind. property/block_superfund covers contaminated sites and property/block_hcri the provider's housing climate risk indicator.

How do I look at a market rather than a property?

Two ways. Set the level to zip, msa, metrodiv or state and pick the components for that level, which give home price and rent indices, affordability and volatility as forecasts and as history. Or use market pulse mode, which reports live listing supply and demand: days on market, list prices, active and new listings, price reductions and months of supply.

What happens if a component has no data for an address?

The provider answers HTTP 200 with a per item outcome code, where 204 means it had nothing, and it does not charge for a 204. This actor records each component's outcome separately in componentStatus, so a row shows exactly which parts came back. A row where nothing came back at all is stored as a miss with the reasons and is not charged.

What happens if my credentials are missing or rejected?

The run ends cleanly with the reason as its status message rather than failing with a stack trace. A missing key, a missing secret, an empty input, credentials the provider will not accept and an exhausted allowance are all treated as answers, not faults. Note that the provider returns a 401 with no explanation, so a wrong key, a wrong secret and a test key used against live data all look identical; the run says so rather than guessing.

Are my credentials stored anywhere?

No. They are read from the run input or from the DATA_API_KEY and DATA_API_SECRET environment secrets, combined into the request's authorization header, and never written to the dataset or the log.

Example output

{
  "recordType": "property",
  "requested": "10216 N Willow Ave, 64157",
  "found": true,
  "slug": "10216-N-Willow-Ave-Kansas-City-MO-64157",
  "address": "10216 N Willow Ave",
  "city": "Kansas City",
  "state": "MO",
  "postalCode": "64157",
  "estimatedValue": 325000,
  "estimatedValueHigh": 340000,
  "estimatedValueLow": 310000,
  "forecastStandardDeviation": 0.05,
  "estimatedRent": 1800,
  "estimatedRentHigh": 1850,
  "estimatedRentLow": 1750,
  "rentForecastStandardDeviation": 0.08,
  "propertyType": "Single Family Residential",
  "bedrooms": 4,
  "bathrooms": 2.5,
  "totalRooms": 8,
  "buildingAreaSqFt": 2104,
  "lotAreaAcres": 0.23,
  "yearBuilt": 2004,
  "componentStatus": {
    "property/value": "ok",
    "property/rental_value": "ok",
    "property/details": "ok"
  }
}

Keyword map

home value estimate API, AVM API, automated valuation model, property valuation API, house price estimate API, rental estimate API, rent estimate by address, forecast standard deviation, property characteristics API, sales history API, tax history API, home price index API, HPI forecast API, rental price index, affordability index API, housing market data API, days on market data, months of supply, listing supply and demand, flood risk by address, hazard risk data, loan to value API, mortgage lien data, notice of default data, owner occupancy data, real estate analytics API, bulk property valuation