> ## Documentation Index
> Fetch the complete documentation index at: https://docs.acrelens.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Analysis modes

> Four evaluation lenses — pick the one that matches what your users are trying to decide.

Every `POST /v1/analyze` request requires a `mode` parameter. The mode controls which sub-scores the report returns, which research questions get asked, and how the AI scoring weights each factor. The overall score comes back the same shape regardless of mode — it's the *composition* underneath that changes.

Choose the mode that matches the decision your user is making.

## The four modes

### `off_grid`

For buyers asking *"Can I live here independent of utilities?"*

| Sub-score | What it measures |
| - | - |
| `solar` | Annual insolation, seasonal variation, panel orientation feasibility |
| `water` | Well drilling viability, surface sources, water rights |
| `septic` | Soil percolation, lot size for drain field, regulatory feasibility |
| `building_codes` | County permitting friction for alternative builds |
| `access` | Year-round road access, distance to plowed roads, slope |

### `rural_residential`

For buyers asking *"Can I build a primary residence here without surprises?"*

| Sub-score | What it measures |
| - | - |
| `utilities` | Distance to and cost of grid power, municipal water, fiber |
| `build_cost` | Site prep, foundation, drive, utility hookup costs |
| `flood_fire_risk` | FEMA flood zone, wildfire history, insurance availability |
| `permit_complexity` | County process, expected timeline to break ground |
| `access` | Same as off-grid: road type, seasonal access, slope |

### `recreational`

For buyers asking *"Will this be a good hunting / camping / weekend property?"*

| Sub-score | What it measures |
| - | - |
| `terrain` | Topography, usable acreage vs. unusable slope |
| `water_features` | Streams, ponds, springs, riparian rights |
| `cover` | Timber, brush, habitat for wildlife |
| `neighboring_use` | Adjacent land use, nearby conflicts (industrial, dense residential) |
| `seasonal_access` | Whether you can get there in winter / wet season |

### `investment`

For buyers asking *"Is this a good buy from a returns perspective?"*

| Sub-score | What it measures |
| - | - |
| `zoning` | Current zoning, likelihood of upzone, restrictions |
| `comps` | Recent local comparable sales |
| `price_per_acre` | Listing price vs. local median |
| `holding_cost` | Property tax, expected annual cost to hold |
| `development_potential` | Subdivide-ability, road frontage, utility access for build-out |

## Score scale

All sub-scores and the overall score are integers `0–100`. The API also returns a `confidence` value per sub-score:

| Confidence | Meaning |
| - | - |
| `high` | Score derived from authoritative public data (NREL, FEMA, USGS, county records) |
| `medium` | Score derived from secondary or aggregated sources |
| `low` | Score derived from inference where direct data was unavailable |

Treat `low` confidence sub-scores as directional — surface them in your UI but don't make irreversible decisions on them.

## Mixing modes in batch requests

`POST /v1/batch` accepts up to 50 items, and each item declares its own `mode`. So a single batch can return one off-grid report and one investment report on the same parcel — useful when comparing perspectives. See [batch analysis](/guides/batch-analysis).

## Picking a mode

If you're building a single-purpose product (off-grid marketplace, hunting-land MLS, etc.), pick one mode and stick to it. If you're building a generalist tool, expose mode selection to your end-users — they know what decision they're making better than your code does.

When in doubt, `rural_residential` is the safest default — its sub-scores cover the majority of what most buyers care about regardless of intent.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.