select a Hover deliverable type and retrieve roof measurement data for a completed job
domain: developers.hover.to · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
When creating a job or capture request, set deliverable_id to the output you need (2 = Roof Only, 3 = Complete, 5 = Total Living Area Plus, 6 = Total Living Area, 7 = Capture Only, 8 = Interior)
Wait for a job-state-changed-v2 webhook (or poll) reporting state=completed, meaning at least one model on the job finished successfully
Use the job/model IDs to call Hover's data endpoints for the format you need: measurement PDF, JSON, XLSX, images, checklist, or material list data
For properties with multiple structures, handle a separate model-created and model-state-changed event per structure since each has independent deliverables
Check model-level state in addition to job-level state — a job can show completed while individual models show failed
Known gotchas
The deliverable_id set at job/capture-request creation determines what the pipeline produces — requesting Roof Only (2) will not later yield wall/siding measurements without a new deliverable change request
A job's overall state can be completed even when some models failed — check each model-state-changed event rather than trusting job state alone
Interior deliverables (8) return a floor-plan sketch and different measurement fields than exterior roof/wall deliverables — branch your parsing logic by deliverable type
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?