IQLand

Retrieve full details for a single architectural plan by its ID. `plan_id` is the plan's UUID `id` — the value in the `id` field of the `recommended_plans` / `sample_plans` returned by `smartbuild` and `overview`. Returns the plan's specs, floor-plan / elevation images, and purchase URL. Note on Plan Numbers: users usually reference a plan by its Plan Number (e.g. "70667MK"), which appears as `plan_number` next to the `id` in any prior smartbuild / overview result — pass the matching `id` here. Looking a plan up by Plan Number alone (with no prior result in context) isn't supported yet.

get_plan

Run a full build-feasibility analysis for a parcel address. Pass a parcel street address. SmartBuild chains the IQland services: 1. Resolves the parcel and pulls its geometry + setbacks to compute the buildable envelope (buildable area, width, depth). 2. Fetches the parcel's zoning regulations. 3. Computes the optimal floor-area band from comparable sales. 4. Finds architectural plans that fit the buildable envelope and band. 5. Returns valuation/KPIs (cost, value, equity) for the top-ranked plan. `build_quality` drives both plan ranking and the construction-cost / equity figures (ECONOMY < STANDARD < PREMIUM < LUXURY). `land_acquisition_cost` is the parcel's purchase/listing price and is fed into the equity model (equity = projected value − construction cost − acquisition cost); pass 0 only if it's truly unknown. INTERACTIVE — both `build_quality` and `land_acquisition_cost` are required and have NO defaults. If you call without either, this returns `status: "needs_input"` with the exact questions to ask the user; ask them, then re-call with the answers. Don't guess — these materially change cost and equity. The chosen values are echoed back under `inputs`. Returns structured data only (no narrative): `inputs`, `buildable_envelope`, `zoning_regulations`, `optimal_area`, `recommended_plans` (top 4 — present the `more_plans.url` SmartBuild link for the full library), `selected_plan_id`, and `valuation`. Requires a specific parcel address — a bare city/zip is rejected. Per-step failures appear under `errors`. To pull full details for one plan, pass its `id` to `get_plan`.

smartbuild

Generate an IQ appraisal report for a subject property. Produces a full appraisal (cost approach + comparable sales with per-comp adjustments, zoning/flood context, and valuation) for the subject described by the parameters. WORKFLOW — call `get_property_info` for the address FIRST. It returns an `appraisal_inputs` block (parcel_id, property_type, year_built, gross_living_area, bedrooms, bathrooms_full, stories, lat, lon) pre-filled from the parcel + listing data. Use those values here rather than guessing. INTERACTIVE — the inputs that are NOT derivable from the parcel/listing, `build_quality` (ECONOMY / STANDARD / PREMIUM) and `land_acquisition_cost`, have no defaults. If you call without them, this returns `status: "needs_input"` with the questions to ask the user; ask them (and confirm any subject field `get_property_info` flagged as missing), then re-call with the answers. VACANT LAND — when `property_type` denotes vacant land (e.g. "Vacant Land", "Land", "Lot"), the improvement fields (year_built, gross_living_area, bedrooms, bathrooms_full, stories) and build_quality describe a building that does not exist, so they are NOT required and are NOT asked for. For every OTHER property type, those structural fields are required: if any is missing this returns `needs_input` asking the user to supply them. Required: address, parcel_id, type ("parcel" | "property" | "plan"), property_type (e.g. "Single Family"), lat, lon. For non-land property types also: build_quality, year_built, gross_living_area (sqft), bedrooms, bathrooms_full, stories. When type="plan", also pass architectural_plan_id. Optional report inputs (owner/site/improvement details) can be passed as named args or via `extra` — a dict of any additional /appraisal_iq fields such as topography, views, foundation_type, roof_surface, exterior_walls, window_type, floors, interior_walls, heating_system, cooling_system, appliances, etc. User-selected values override system-derived ones. Returns the structured appraisal report (no narrative).

Estimate the construction cost of a building. Computes a localized construction cost estimate from the gross floor area (sqft), build quality, story count and basement/garage configuration for a given state and county.

Find parcels matching a street address. Returns candidate parcels with parcel_id, address, city, state, zip and county. Use this first to resolve a free-text address into a parcel_id that the zoning and cost tools require.

Get comparable sales (comps) for a property. Returns recent comparable sales near a subject property, for valuation and appraisal context. Identify the subject one of three ways (in priority order): a `property_id`, a `parcel_id` (a `state` is required — it is inferred from the address when omitted), or just an `address` (resolved to a parcel automatically). Passing an address is the simplest — you don't need a parcel_id first.

Get development KPIs for a property. Returns headline development metrics (estimated cost, value, margin and related KPIs) for a property, combining construction cost with land cost. INTERACTIVE — `build_quality` and `land_acquisition_cost` materially change the equity/margin KPIs and have no defaults. If you call without them, this returns `status: "needs_input"` with questions to ask the user; ask, then re-call with the answers (pass land_acquisition_cost=0 to exclude land).

Find the highest-resale-value building plan for a property. Returns the architectural plan projected to yield the highest resale value for the given parcel/address.

Recommend the optimal buildable area for a parcel. Returns the suggested gross floor area that maximizes development value given local zoning and cost conditions.

Get detailed zoning info for a parcel. Returns the parcel's zoning_code, lot area, owner and coordinates, plus `regulations_table` — a ready-to-render markdown table of the district standards that actually govern the parcel (setbacks, height, FAR, lot minimums), with any overlay district's adjustments applied. Requires a parcel_id (use find_parcel to obtain one).