The REIzer deal-analysis API

Quickstart — one curl, no key

$ curl -X POST https://reizer.io/api/v1/analyze \
    -H "Content-Type: application/json" \
    -d '{"strategy":"ltr","inputs":{"price":285000,"marketRent":3100,
         "downPct":0.25,"rate":0.0675}}'

{
  "score": 96, "verdict": "Strong",
  "metrics": { "monthly_cash_flow": 636.85, "dscr": 1.4594,
               "cap_rate": 0.0852, "cash_on_cash": 0.0989, … },
  "stress": [ 7 scenarios, each with a verdict ],
  "thresholds": { "break_even_rent": 2282.47, "max_rate": 0.0878, … },
  "assumptions": { "estimated_fields": ["taxes", "insurance", …] },
  "summary": "Strong (96/100). $637/mo cash flow, DSCR 1.46, …",
  "report_url": "https://reizer.io/report.html?id=…"
}

Endpoints

Input rules

• camelCase keys, dollars as plain numbers. Discover every strategy's fields at GET /api/v1/strategies.
• Rates and percents are fractions — 0.0675, never 6.75. Percent-style values are rejected with an error naming the field, never silently converted.
• Omitted inputs get documented defaults. REIzer fills a documented default and lists every estimated field under assumptions.estimated_fields, so a caller (or its user) knows exactly what was assumed. Invalid values are rejected, never replaced.
• Minimum inputs per strategy: ltr price + marketRent · str price + adr + occupancy · brrr price + rehabBudget + marketRent + arv · multifamily price + units · flip price + rehabBudget + arv · newc landPrice + livingSqft + buildPsf + btsArv.

Money-field units

Dollar inputs use these periods (same on every strategy, including STR). Percents stay fractions as above. Discover the full schema at GET /api/v1/strategies.

Changelog (2026-08-16): hoa is monthly on every strategy, including STR. Earlier engine builds treated STR HOA as annual; callers that inferred that from behaviour should send monthly dollars going forward. API_VERSION remains v1 — the old annual-STR behaviour was never documented.

Best-use ranking

Send one property's inputs as a superset; strategies missing required fields are skipped with the reason:

"best_use": "ltr"
"ranked":  1. ltr 91 · 2. str 77 · 3. brrr 29 · 4. flip 5
"skipped": multifamily, newc  (missing unit / land inputs)

Max allowable offer

Targets are optional — rentals default to cash-on-cash ≥ 8%, DSCR ≥ 1.2, cash flow ≥ $0; flips to after-tax margin ≥ 10% and annualized ROI ≥ 15%; BRRRR adds capital recovery ≥ 80%. The response names the binding constraint and each target's individual price ceiling:

"mao": 303657   "binding_constraint": "cash-on-cash return ≥ 8%"
"metrics_at_mao": { "monthlyCF": 546.10, "dscr": 1.3697 }
"ceilings_per_target": { "cocReturn": 303657, "dscr": 346599, "monthlyCF": 333691 }

Beyond the defaults, each strategy accepts optional targets that bind only when you name them: capRate on rentals and STR (plus dscr on STR), afterTaxProfit and rule70 on flips, and coc, cashLeft and rule70 on BRRRR. cashLeft is a ceiling, not a floor — the solve keeps cash left in the deal at or below your number. BRRRR metrics depend on which refinance you underwrite to, so "scenario": "refiLTV1" | "refiLTV2" | "refiLTV3" picks one; omit it and the engine's winning scenario is used.

Shareable reports

Every /analyze response carries a report_url — a public report page (score gauge, metrics, stress table) that needs no account to view and expires after 30 days. Built to be handed to the person you're advising; GET /api/v1/reports/:id serves the underlying data.

/analyze takes two optional blocks that only affect that page. property — name, address, city, county, state, zip, beds, baths, sqft, type — puts a header and a map on the report; anything else in it is dropped, and nothing in it reaches the analysis. mao — { "targets": { … }, "scenario": "…" } — adds a max-allowable-offer section, re-solved server-side from the same inputs. A MAO that can't be solved drops the section rather than failing the analysis.

Keyed endpoints — licensed data

Analysis runs on REIzer's own engine and stays free. What costs money — licensed comps and STR market data — needs an API key from a paid plan (Investor and up), metered against the same monthly allowances as the web app. Create keys under Settings → API keys; send them as X-API-Key or Authorization: Bearer.

$ curl -X POST https://reizer.io/api/v1/comps \
    -H "Content-Type: application/json" \
    -H "X-API-Key: rz_live_…" \
    -d '{"action":"comps",
         "address":{"street":"4917 Maple Ave","city":"Dallas","state":"TX"},
         "options":{"saleCount":10,"rentCount":10}}'

The comps body takes a nested address object (a flat street/city/state body returns an empty result, not an error). /api/v1/comps returns comparable sales with a value estimate and range, rental comps with a rent estimate, and ZIP-level market stats. /api/v1/str-comps takes latitude/longitude (+ optional bedrooms) and returns nearby STR listings with ADR, occupancy, and revenue quartiles. Full argument tables: tool catalog — the REST bodies match the MCP tool arguments.

Keys are shown once at creation, revocable instantly, and the plan is resolved live on every call — a downgrade or revocation takes effect immediately.

Rate limits & errors

FAQ