> For the complete documentation index, see [llms.txt](https://docs.alphageo.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.alphageo.ai/for-developers/alphageo-data-api/financial-impact-analytics-api.md).

# Financial Impact Analytics API

This endpoint provides data for real estate cashflow modelling. The metrics translate climate risk and resilience features into various cashflow items such as rate of increase in insurance, projected utility costs, and exit-cap-rate adjustments.

The climate indicators used for the 2025 baseline primarily come from ERA5-Land reanalysis averaged over 2020–2025, with coverage fallbacks. Other hazards retain source-specific baselines. Baseline physical inputs are shared across scenarios, while financial impacts can differ because the future conditions vary by scenario. See the [source and baseline FAQ](/faqs/data-products-faq.md).

## Endpoint

<pre class="language-rest"><code class="lang-rest"><strong>GET https://app.alphageo.ai/api/public/v1/analytics
</strong></code></pre>

## Parameters

<table><thead><tr><th>Parameters</th><th data-type="checkbox">Required</th><th>Type</th><th>Description</th></tr></thead><tbody><tr><td>asset_id</td><td>false</td><td>string (UUID)</td><td>The unique identifier of an asset uploaded to your institution's account.</td></tr><tr><td>address</td><td>false</td><td>string</td><td>Full address of the location</td></tr><tr><td>scenario</td><td>true</td><td>string</td><td><p>Identifier for CMIP6 Emission Scenarios.</p><p><em>Available values</em> : SSP245, SSP370, SSP585</p></td></tr><tr><td>longitude</td><td>false</td><td>number</td><td>Longitude of the location that being queried.</td></tr><tr><td>latitude</td><td>false</td><td>number</td><td>Latitude of the location that being queried.</td></tr></tbody></table>

### Query Validation Priority

When calling these endpoints, you must provide **at least one** way to identify the location. If multiple parameters are supplied, the API resolves the query using the following precedence:

1. **`asset_id`**: If provided, the API looks up the asset under your institution's profile.
2. **`latitude` & `longitude`**: If `asset_id` is not provided, the API looks up data by coordinates.
3. **`address`**: If neither of the above are provided, the API performs geocoding to resolve coordinates.

If none of these parameters are supplied, the API returns a `400 Bad Request` with an error message.

## Example requests

#### cURL

```bash
$ curl --location 'https://app.alphageo.ai/api/public/v1/analytics?longitude=-97.2805288&latitude=32.7376509&scenario=SSP245' \
--header 'Authorization: YOUR_API_TOKEN'
```

#### Python

```python
import requests

url = "https://app.alphageo.ai/api/public/v1/analytics?longitude=-97.2805288&latitude=32.7376509&scenario=SSP245"

payload = {}
headers = {
  'Authorization': 'YOUR_API_TOKEN'
}

response = requests.request("GET", url, headers=headers, data=payload)

print(response.text)

```

### Insurance field interpretation

`INS_RATE_FIRE` and `INS_RATE_FLOOD` are the annualized climate-driven premium-growth contributions from wildfire and combined inland/coastal flooding over 2025–2050. `INS_RATE_ANNUAL` is their sum. Values are percentages per year: `2` means 2% annual growth. Stable or declining impacts contribute zero growth.

## Example response

The response below illustrates the field structure. Values are illustrative and do not represent a current assessment of the requested location or portfolio. `<current data version>` is a placeholder for the service’s configured `data_version` label.

A successful response containing analytics of the given location.

```json
{
  "identifiers": {
    "SCENARIO": "SSP245"
  },
  "insurance": {
    "INS_RATE_FIRE": 0,
    "INS_RATE_FLOOD": 0.0,
    "INS_RATE_ANNUAL": 0.0
  },
  "utility": {
    "UTIL_RATE_COOLING": 0.38,
    "UTIL_RATE_HEATING": -0.41,
    "UTIL_RATE_ANNUAL": -0.03
  },
  "capex": {
    "CAPEX_FIRE": 0,
    "CAPEX_FLOOD": 0,
    "CAPEX_CDD": 0,
    "CAPEX_ANNUAL": 0
  },
  "discount": {
    "10_YEAR_DISCOUNT": 0.09,
    "25_YEAR_DISCOUNT": 0.22,
    "75_YEAR_DISCOUNT": 0.38
  },
  "operation_downtime": {
    "DOWNTIME_DAYS_ANNUAL": 0.08
  },
  "operation_efficiency": {
    "EFFICIENCY_LOSS_ANNUAL": 0.68
  },
  "workforce_productivity": {
    "PRODUCTIVITY_LOSS_ANNUAL": 1.26
  },
  "maintenance_cost": {
    "MAINT_RATE_ANNUAL": -0.04
  },
  "insurability": {
    "UNINSURABLE_COASTAL": 0,
    "UNINSURABLE_FIRE": 0,
    "UNINSURABLE_INLAND": 0,
    "UNINSURABLE_TOTAL": 0
  },
  "data_version": "<current data version>"
}
```

### Horizons and valuation outputs

This endpoint takes a scenario without a `period` parameter. Growth metrics use their defined calculation horizons. `10_YEAR_DISCOUNT`, `25_YEAR_DISCOUNT` and `75_YEAR_DISCOUNT` are exit-cap-rate adjustments for 2035, 2050 and 2100, expressed in percentage points: `0.25` increases a 5% exit cap rate to 5.25%. The DCF discount rate remains unchanged.

The Financial Impact download additionally provides `10Y_NPV`, `AAL` and `ADPT_ALPHA`. These valuation outputs are not returned by this public endpoint. See the [worked valuation example](/climate-resilience-suite-crs/use-cases/use-case-alphageo-for-climate-adjusted-valuation.md) and [data dictionary guide](/for-developers/data-dictionary.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.alphageo.ai/for-developers/alphageo-data-api/financial-impact-analytics-api.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.