The underwriting survey, as an API

Territas answers a single question a lender or investor asks about a property: what is the risk-adjusted picture of this parcel, and where did each number come from? You send an address and the deal’s economics; you get one JSON response that surveys the site — draws the parcel, drops the FEMA flood zone, reads elevation and slope, scores wildfire and the National Risk Index, pulls Census demographics, and folds it all into a risk-adjusted net operating income. Every field carries its source and an as_of date, so the answer is audit-ready rather than a score you have to trust.

The three public endpoints

POST/v1/underwrite — underwrite a single property. This is the call you’ll reach for first; the Quickstart runs it end to end.

POST/v1/bulk-underwrite — underwrite up to 500 properties in one request, with a summary and per-row results. This is the engine behind the CSV-into-Excel workflow; see Batch & CSV.

GET/health — an unauthenticated liveness probe. Everything else requires an API key.

What a response contains

Each underwrite returns these sections, every one stamped with its federal source:

• parcel — matched address, county FIPS and name, census tract, state.
• elevation — ground elevation and slope from USGS.
• flood — FEMA zone, subtype, risk label, base flood elevation, panel ID.
• flood_insurance_requirement — whether NFIP coverage is mandated, the citation, SFHA status, community participation and CRS discount, and the minimum coverage.
• climate_wildfire and national_risk_index — wildfire percentile and rating, plus FEMA NRI hazard ratings and expected-loss ratios by peril.
• demographics — median household income and home value from the Census Bureau.
• financials_risk_adjusted — the deal math: required flood premium folded in, risk-adjusted NOI, and the assumptions behind it.
• audit and warnings — the provenance trail and any caveats for this specific parcel.

The full field-by-field shape lives in the interactive API reference, which you can read against the live schema.

Getting started

Create a key, make your first underwrite, then decide whether you’re working one deal at a time or a whole book:

• Quickstart — your first key and first underwrite in a few minutes.
• Authentication — how keys and the X-API-Key header work.
• Batch & CSV — score a spreadsheet of addresses and read the results back into Excel.
• MCP server — expose the same underwriting tools to Claude and other agents.