niche · -1.6 capability resource

Disaster Recovery

Score 18.3 / 100 38 providers +7 via APIs 14 APIs Search apis.io →

Providers using this tag (38)

Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.

Exemplar 2 Complete, well-documented, and agent-ready
Developing 9 Usable, with meaningful gaps to close
Thin 13 Limited public surface area
Emerging 6 Early or largely undocumented
Minimal 6 Almost no public developer surface
Unrated 2 Not yet scored

APIs with this tag (14)

Ranked by the provider's API Evangelist rating — the Kin Score is scored per provider, not per API, so every API of a provider shares its band. How the rating works →

Exemplar 1 Complete, well-documented, and agent-ready
Strong 2 Solid coverage with minor gaps
Developing 8 Usable, with meaningful gaps to close
Thin 3 Limited public surface area

Companies reaching this through an API (7)

These companies publish an API, specification or operation carrying “Disaster Recovery” but do not classify their business under it. Listed unranked and kept out of the count above, because one tagged operation is not a statement about what a company does.

Azure Database for MySQL Azure Migrate Delinea Oracle Oracle Enterprise Manager VMware Yugabyte

Score breakdown

Frequency
46.1
log-scaled weighted occurrences
Breadth
0.9
spread across providers
Quality lift
32.9
mean composite of providers using it
Cohesion
0.0
strength of nearest seed neighbor

Related tags

Data Protection 29 co-occurrences Backup 26 co-occurrences Business Continuity 7 co-occurrences VMware 7 co-occurrences Storage Management 5 co-occurrences Replication 7 co-occurrences Failover 5 co-occurrences

Where this tag comes from

Provider tag39
Api tag14

Cohort brief

Auto-generated

The 33 providers in the APIs.io catalog tagged Disaster Recovery, scored on the Kin Score. Every figure below is computed from the catalog — nothing here is written.

Providers
33
of 38 in the catalog
Mean Kin Score
34.2
+12.0 vs catalog 22.2
Mean Agent Readiness
18.1
+6.1 vs catalog 12
Spread
6.8–82.9
median 35.6 · σ 16.5
How the 33 split by band
Exemplar 2Strong 0Developing 9Thin 13Emerging 6Minimal 3
Facet averages, against the whole catalog
FacetThis cohortCatalogDifferenceScored
Developer Ergonomics 41.8 23.2 +18.6 33
Access Clarity 35.6 23.9 +11.7 33
Operational Transparency 23.8 13 +10.8 33
Contract Quality 26.4 17.2 +9.2 33
Discoverability 63.2 57.9 +5.3 33
Contract Governance 7.6 6.5 +1.1 33

A facet is averaged over the members that carry it, not over the whole cohort — the “Scored” column is that count. Averaging an absent facet as zero would score our own coverage gaps as the providers’ posture.

What this cohort publishes
ArtifactThis cohortCatalogDifference
MCP server (any) 17% 13% +4
MCP server (first-party) 17% 12% +5
Agent Skills 0% 0% 0
OAuth scopes 23% 11% +12
Security 91% 98% -7
Arazzo workflows 0% 2% -2
Governance rules 14% 16% -2

mcp_pct counts any mcp/ artifact including ones API Evangelist derived from the provider OpenAPI; mcp_first_party_pct counts only servers the provider publishes. Prefer the latter.

Top by Kin Score
  1. 1 Acronis 82.9
  2. 2 Cohesity 68.4
  3. 3 Druva 53.7
  4. 4 Veritas NetBackup 52.7
  5. 5 Slide 48.3
  6. 6 Cutover 46.9
  7. 7 Eon 44.3
  8. 8 Datto 43.2
  9. 9 Unitrends 41.4
  10. 10 Veritas InfoScale 39.8
Top by Agent Readiness
  1. 1 Druva 56.2
  2. 2 Acronis 55.2
  3. 3 Cohesity 40.8
  4. 4 Veeam 38.3
  5. 5 Eon 35.5
  6. 6 Veritas NetBackup 32.6
  7. 7 Unitrends 30.7
  8. 8 Amazon Resilience Hub 30.2
  9. 9 Datto 27.7
  10. 10 Cutover 26.1
All 38 members of this roster resolve to a provider in the catalog; 33 carry a score (87%). The figures above describe the scored members only.
Coverage caveat. 30 of 33 scored members had under half their catalog-attributable points satisfied at all (catalog_earned / catalog_max < 0.5). They are INCLUDED in the mean above. A large share here means the cohort mean is partly a measurement of how far our enrichment reached, not only of how these providers publish.Generated from the catalog build of 24 October 2026, across 31984 providers, using the same computation served by the APIs.io cohort API. Briefs are published for rosters of 5 or more scored providers; below that a distribution is not meaningful.

Work with this as data

Every tag 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 tags

7 MCP tools reach this
  • find_tagsBrowse and filter every tag in the catalog.
  • get_cohortThis tag as a scored cohort — every provider carrying it, with scores.
  • cohort_statsPRO — the distribution across this tag: mean, median, band split, adoption rates.
  • cohort_rankingsPRO — the leaderboard, on composite AND agent-readiness axes.
  • 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 tag
curl "https://apis.io/api/v1/tags/disaster-recovery"
All tags
curl "https://apis.io/api/v1/tags?limit=25"
As a scored cohort
curl "https://apis.io/api/v1/cohorts/tag/disaster-recovery"
The distribution (Pro)
curl "https://apis.io/api/v1/cohorts/tag/disaster-recovery/stats" \
  -H "X-API-Key: $APIS_IO_KEY"

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.

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