One Concern

One Concern is a Palo Alto, California climate-resilience analytics company that builds a digital twin of the built environment to quantify physical climate and natural-catastrophe risk in units of time rather than broad-brush hazard bands. Its Domino AI platform models the recovery of an individual building together with the lifelines it depends on — power distribution, ports, airports, roads and bridges, the surrounding residential community — and returns business-interruption downtime statistics, property-damage ratios and a 1CRX resilience score for a given latitude and longitude, per peril (flood, tropical-cyclone wind, seismic ground shaking, or all perils integrated), per return period or planning horizon, and under baseline or 2050 climate-change scenarios. The company sells to insurers, reinsurers, financial services and real estate, and exposes the platform to customers through the Domino AI API, a five-operation REST contract documented at developer.oneconcern.com and served from api.oneconcern.com behind a Tyk gateway with a customer-issued x-1c-api-token header.

One Concern publishes 1 API contract indexed on the APIs.io network: Location API. Tagged areas include Climate Risk, Catastrophe Modeling, Resilience, Insurance, and Reinsurance.

The One Concern catalog on APIs.io includes 1 Spectral governance ruleset.

One Concern’s developer surface includes documentation, API reference, getting-started guide, engineering blog, support, and 18 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

35.4/100 thin ▬ flat Agent 29/100 agent ready saas Full breakdown ↓
scored 2026-11-02 · rubric v0.26.0 · Show this score on your site →

AccessOpen

1 published contract 2 Agent Skills

Climate Risk Catastrophe Modeling Resilience Insurance Reinsurance Risk Analytics GeospatialBusiness InterruptionReal Estate Financial Services Artificial Intelligence

What this lets a business do 1

Business capabilities this provider's published APIs can perform, derived from its own contracts. Browse all capabilities →

Real Estate Asset Management

BC-4920

Location

POST /v1/location/property-damage/return-period

Kin Score

Kin Score How this is scored →
scored 2026-11-02 · rubric v0.26.0

Composite quality — 35.4/100 · thin

Contract Quality 7.8 / 19

Developer Ergonomics 8.8 / 15

Access Clarity 3.2 / 15

Operational Transparency 0.3 / 10

Contract Governance 1.6 / 9

Discoverability 5.0 / 8

Regulatory Posture 3.1 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 29/100 · agent ready

Machine-Readable Contract 18 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 0 / 6

Agent Skills 5 / 5

Well-Known Catalog 4 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Insurance regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/one-concern/"><img src="https://apis.io/badge/one-concern/card.svg" alt="One Concern on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Request/Response Examples +7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document

7 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Access Clarity scores 21.1 — up to +15.8 composite points
Contract Quality scores 41.6 — up to +14.6 composite points
Operational Transparency scores 2.6 — up to +12.7 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/one-concern/apis.yml: open an issue on github.com/api-evangelist/one-concern to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Standards implemented 1

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

OpenAPI

measured — observed by APIs.io (published)

APIs 1

Individual APIs this provider publishes, each with its own machine-readable definition.

One Concern Location API

The Location API from One Concern — 5 operation(s) for location.

Agent Skills 2

Packaged agent skills for driving this provider's APIs from an AI assistant.

compare-property-damage-scenarios

AGENT SKILL

score-location-business-interruption

AGENT SKILL

Pricing Plans 1

Published pricing tiers and plan structures.

One Concern Plans Pricing

0 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

One Concern Rate Limits

0 limits

RATE LIMITS

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

One Concern API Rules

45 rules · 43 errors 1 warnings 1 info

SPECTRAL

OpenAPI Overlays 1

Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.

One Concern Domino Ai Overlay

17 actions · servers

DERIVED

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

One Concern Authentication

3 schemes

SECURITY

One Concern Domain Security

TLSv1.3 · DNSSEC

SECURITY

Resources

Get Started 2

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

GettingStarted

GettingStarted

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

AgentSkill

AgentSkill

WellKnownProbe

WellKnownProbe

LLMsTxt

LLMsTxt

Build 2

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

GitHubOrganization

Packages

Packages

Access & Security 1

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Operate 2

Status, limits, changes, and where to get help

RateLimits

RateLimits

Support

Support

Commercial 3

Pricing, plans, and the legal terms of use

Plans

Plans

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Company 5

The organization behind the API

Website

Blog

BlogRSS

About

LinkedIn

Other 3

Properties that don't map to a standard resource type

CapabilityMap

CapabilityMap

Overlay

Overlay

Products

Products

Source (apis.yml)

aid: one-concern
name: One Concern
description: One Concern is a Palo Alto, California climate-resilience analytics company that builds a digital twin of the
  built environment to quantify physical climate and natural-catastrophe risk in units of time rather than broad-brush hazard
  bands. Its Domino AI platform models the recovery of an individual building together with the lifelines it depends on —
  power distribution, ports, airports, roads and bridges, the surrounding residential community — and returns business-interruption
  downtime statistics, property-damage ratios and a 1CRX resilience score for a given latitude and longitude, per peril (flood,
  tropical-cyclone wind, seismic ground shaking, or all perils integrated), per return period or planning horizon, and under
  baseline or 2050 climate-change scenarios. The company sells to insurers, reinsurers, financial services and real estate,
  and exposes the platform to customers through the Domino AI API, a five-operation REST contract documented at developer.oneconcern.com
  and served from api.oneconcern.com behind a Tyk gateway with a customer-issued x-1c-api-token header.
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: open
  trial: false
  try_now: false
  public: true
  gated: none
  gated_source:
  - onboarding
  label: Open access
  confidence: medium
  source:
  - authentication
  - rate-limits
  - security
  generated: '2026-11-02'
  method: derived
image: https://oneconcern.com/wp-content/uploads/2021/10/One-Concern-Logo.png
url: https://raw.githubusercontent.com/api-evangelist/one-concern/refs/heads/main/apis.yml
x-type: company
x-source: harvest:secondary-market
specificationVersion: '0.20'
created: '2026-08-26'
modified: '2026-08-26'
tags:
- Climate Risk
- Catastrophe Modeling
- Resilience
- Insurance
- Reinsurance
- Risk Analytics
- Geospatial
- Business Interruption
- Real Estate
- Financial Services
- Artificial Intelligence
tags_raw:
- Climate Risk
- Catastrophe Modeling
- Resilience
- Insurance
- Reinsurance
- Risk Analytics
- Geospatial
- Business Interruption
- Real Estate
- Financial Services
- Artificial Intelligence
- Real-Estate
- Financial-Services
apis:
- aid: one-concern:one-concern-location-api
  name: One Concern Location API
  description: The Location API from One Concern — 5 operation(s) for location.
  humanURL: https://developer.oneconcern.com/overview
  baseURL: https://api.oneconcern.com
  tags:
  - Location
  properties:
  - type: OpenAPI
    url: openapi/one-concern-location-api-openapi.yml
  - type: Documentation
    url: https://developer.oneconcern.com/overview
  - type: APIReference
    url: https://developer.oneconcern.com/api-spec
  - type: GettingStarted
    url: https://developer.oneconcern.com/overview
  - type: Authentication
    url: authentication/one-concern-authentication.yml
  - type: Conventions
    url: conventions/one-concern-conventions.yml
  - type: ErrorCatalog
    url: errors/one-concern-problem-types.yml
  - type: DataModel
    url: data-model/one-concern-data-model.yml
  - type: Lifecycle
    url: lifecycle/one-concern-lifecycle.yml
  - type: Conformance
    url: conformance/one-concern-conformance.yml
  - type: RateLimits
    url: rate-limits/one-concern-rate-limits.yml
  - type: Plans
    url: plans/one-concern-plans-pricing.yml
  - type: MCPCandidate
    url: mcp/one-concern-mcp.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Plans
  url: plans/one-concern-plans-pricing.yml
- type: RateLimits
  url: rate-limits/one-concern-rate-limits.yml
- type: CapabilityMap
  url: capabilities/one-concern-capability-edges.yml
  name: One Concern Business Capability Map
- type: Overlay
  url: overlays/one-concern-domino-ai-overlay.yaml
- type: AgentSkill
  url: skills/_index.yml
- type: Website
  url: https://oneconcern.com/en/
- type: DeveloperPortal
  url: https://developer.oneconcern.com/overview
- type: Documentation
  url: https://developer.oneconcern.com/overview
- type: APIReference
  url: https://developer.oneconcern.com/api-spec
- type: GettingStarted
  url: https://developer.oneconcern.com/overview
- type: Blog
  url: https://oneconcern.com/en/news/
- type: BlogRSS
  url: https://oneconcern.com/feed/
- type: Support
  url: https://oneconcern.com/en/contact/
- type: GitHubOrganization
  url: https://github.com/oneconcern
- type: TermsOfService
  url: https://oneconcern.com/en/terms/
- type: PrivacyPolicy
  url: https://oneconcern.com/en/privacy/
- type: About
  url: https://oneconcern.com/en/about/
- type: Products
  url: https://oneconcern.com/en/products/
- type: LinkedIn
  url: https://www.linkedin.com/company/oneconcern/
- type: Packages
  url: packages/one-concern-packages.yml
- type: WellKnownProbe
  url: well-known/one-concern-well-known.yml
- type: LLMsTxt
  url: llms/one-concern-llms.txt
- type: DomainSecurity
  url: security/one-concern-domain-security.yml
x-enrichment:
  date: '2026-08-26'
  status: enriched
  artifacts_added: 19
  pass: local-v1

One Concern API — frequently asked questions

Does One Concern have an API?

Yes. APIs.io lists 1 API from One Concern, including One Concern Location API.

Is there an OpenAPI specification for the One Concern API?

Yes. APIs.io indexes 1 OpenAPI specification for One Concern, each linked for download from this page.

How do I authenticate with the One Concern API?

One Concern uses bearer-token authentication (3 schemes). The details are profiled on APIs.io as One Concern Authentication.

Is the One Concern API ready for AI agents?

One Concern has a Kin Score of 35.4 out of 100 (thin) and an Agent Readiness score of 29.0 (agent-ready), scored by API Evangelist on 2026-11-02.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/one-concern"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/one-concern/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/one-concern/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.