Register for API access at housecanary.com; authentication uses HTTP Basic Auth with your API key as the username and your API secret as the password on every request.
The API base URL is documented at api-docs.housecanary.com; endpoints are organized by level (property, block, ZIP, MSA) and by data type (value, risk, rental, forecast).
To fetch an AVM for a single property, call the property/value endpoint with address and zipcode as query parameters; the response includes the estimated value and a high/low confidence range.
For rental valuation, call the property/rental_value endpoint with the same address parameters; the response returns the estimated monthly rent and comparable rental properties.
Batch multiple addresses in a single request using the bulk endpoint variants (up to the limit specified in your plan) to reduce round trips when processing a portfolio.
Use the property/value_forecast endpoint to retrieve projected value changes over a configurable horizon; combine with the canary_rental_index endpoint for gross yield analysis at the ZIP or MSA level.
Known gotchas
HouseCanary API access is tiered by plan; the number of addresses per batch call and the monthly request quota depend on your subscription — check your plan limits before running portfolio-scale pulls.
Address matching requires clean, standardized input; non-standard abbreviations or missing ZIP codes cause no-match responses rather than errors, silently returning empty data.
Legacy endpoints are documented at api-docs-legacy.housecanary.com; the current analytics API at api-docs.housecanary.com has a different structure — do not mix endpoint patterns between the two.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp