# One Concern

> One Concern is a Palo Alto, California climate-resilience analytics company. It builds a digital
> twin of the built environment and quantifies physical climate and natural-catastrophe risk in
> units of time — how long a specific building, and the lifelines it depends on, would be down
> after an event. Its Domino AI platform is sold to insurers, reinsurers, financial services and
> real estate, and is exposed to customers through the Domino AI API.

Generated by API Evangelist on 2026-08-26. One Concern does not publish an llms.txt of its own —
https://oneconcern.com/llms.txt returns 404 and https://developer.oneconcern.com/llms.txt returns
an 87-byte HTML meta-refresh shell (soft-404). This file is generated from the company's public
documentation and from the OpenAPI it publishes; it is not a One Concern artifact.

## API

- [Domino AI API overview](https://developer.oneconcern.com/overview): Getting started,
  authentication, headers, errors and versioning for the Domino AI API.
- [API reference](https://developer.oneconcern.com/api-spec): Rendered reference for all five
  operations and every request/response schema.
- [Calculation process](https://developer.oneconcern.com/calculation-process): Input and output
  field definitions, the risk-binning thresholds, and the downtime methodology.
- [OpenAPI 3.1.0 specification](https://developer.oneconcern.com/openapi.json): Domino AI API
  v1.31.2, five operations, fifteen schemas.

Base URL: https://api.oneconcern.com
Authentication: customer-issued token in the `x-1c-api-token` header, plus a required `client-id`
header used for billing attribution and an optional `transaction-id` header for tracing. Tokens
are issued by One Concern customer success; there is no self-service sign-up.

## Operations

All five are POST, all five are pure reads, and each returns one result for one coordinate pair.

- `POST /v1/location/business-interruption/return-period` — business interruption risk score and
  downtime statistics at a chosen return period (50, 100, 250, 500, 1000 years).
- `POST /v1/location/business-interruption/average-annual` — the same, annualised across all
  return periods.
- `POST /v1/location/business-interruption/planning-horizon` — the same, over a forward planning
  horizon of 1, 5, 10, 20 or 30 years.
- `POST /v1/location/property-damage/return-period` — direct structural damage ratio at a chosen
  return period.
- `POST /v1/location/property-damage/average-annual` — direct structural damage ratio, annualised.

## Vocabulary

- peril: `flood` (inland and coastal flooding), `wind` (tropical cyclone wind), `seismic`
  (earthquake ground shaking), `integrated` (all perils combined). `integrated` is accepted on the
  average-annual and planning-horizon operations only — NOT on return-period operations.
- interruption_type: `integrated`, `utility` (power distribution only), `ingress_egress` (ports,
  airports, roads, bridges), `community` (residential community only), `repair_time` (building
  structural downtime), plus `ports`, `airports`, `bridges`, `highways`.
- climate_change: `ccbaseline` (baseline climate) or `cc2050_45` (RCP 4.5 or equivalent SSP, 2050).
- Risk bands: `high` when downtime >= 7 days, `med` when >= 2 and < 7 days, `low` when < 2 days.

## Things an agent must know

- HTTP 204 No Content is a legitimate answer meaning there is no modeled building within
  `max_distance_m` (1.0 to 500.0 metres) of the supplied coordinates. It is not a failure and
  should not be retried unchanged.
- The API is read-only. Nothing is created, updated or deleted, so retries are safe and no
  reversal or idempotency key is needed.
- Two different error envelopes are in use: `{"error": "..."}` from the gateway for auth failures,
  and `{"detail": [{"loc":…,"msg":…,"type":…}]}` for validation failures.
- Every response carries `x-1c-api-version` and `x-1c-data-version`. Record both if the result
  needs an audit trail; model and data changes are announced through customer success, not a
  public changelog.
- There is no batch or list operation. Scoring a portfolio means one request per location.
- No rate limits, quotas or prices are published.

## Company

- [Website](https://oneconcern.com/en/)
- [About](https://oneconcern.com/en/about/)
- [Products](https://oneconcern.com/en/products/) — Domino AI, Domino, Domino Co-pilot
- [Domino AI product page](https://oneconcern.com/en/products/dna/)
- [News](https://oneconcern.com/en/news/) ([RSS](https://oneconcern.com/feed/))
- [Contact](https://oneconcern.com/en/contact/)
- [GitHub](https://github.com/oneconcern)
- [Terms of Use](https://oneconcern.com/en/terms/)
- [Privacy Policy](https://oneconcern.com/en/privacy/)

## Not published

One Concern publishes no pricing page, no status page, no changelog, no SLA, no deprecation
policy, no sandbox or test credentials, no SDK in any package registry, no MCP server, no A2A
agent card, and no /.well-known/ documents on any host.