Understand what's actually available before trying to self-serve integrate with BuildFax (Verisk) property history data
domain: buildfax.com · 4 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Confirm ownership/branding: BuildFax was acquired by Verisk in 2019 and is now marketed under Verisk's property intelligence solutions (verisk.com/products)
Know what it covers: aggregated building permits, code violations, and construction/renovation history sourced from local jurisdictions
Recognize this is not a self-serve developer product — there is no public signup or published request/response schema; Verisk's API catalog (apicatalog.verisk.com) is a general API design-management portal, not public BuildFax docs
Contact Verisk/BuildFax sales via buildfax.com to scope a data license; delivery is negotiated per account as either an API feed or bulk file delivery
Known gotchas
Do not assume a 'BuildFax API key' can be self-provisioned like a typical SaaS product — this is an enterprise B2B data contract, and public marketing pages do not expose endpoint or field-level documentation
Permit-data coverage is jurisdiction-dependent and varies significantly by county/municipality — confirm coverage for your specific market before contracting
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?