Security Operations
Providers using this tag (49)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 1 Complete, well-documented, and agent-ready
Developing 10 Usable, with meaningful gaps to close
Thin 10 Limited public surface area
Emerging 17 Early or largely undocumented
Minimal 8 Almost no public developer surface
Unrated 1 Not yet scored
APIs with this tag (10)
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 1 Solid coverage with minor gaps
Developing 3 Usable, with meaningful gaps to close
Thin 4 Limited public surface area
Emerging 1 Early or largely undocumented
Companies reaching this through an API (1)
These companies publish an API, specification or operation carrying “Security Operations” 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.
Score breakdown
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 48 providers in the APIs.io catalog tagged Security Operations, scored on the Kin Score. Every figure below is computed from the catalog — nothing here is written.
| Facet | This cohort | Catalog | Difference | Scored |
|---|---|---|---|---|
| Access Clarity | 36.1 | 26.5 | +9.6 | 48 |
| Developer Ergonomics | 27.7 | 23.2 | +4.5 | 48 |
| Discoverability | 62.2 | 58.1 | +4.1 | 48 |
| Operational Transparency | 17.4 | 13.7 | +3.7 | 48 |
| Contract Governance | 8.9 | 6.3 | +2.6 | 48 |
| Contract Quality | 15.3 | 17.6 | -2.3 | 48 |
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.
| Artifact | This cohort | Catalog | Difference |
|---|---|---|---|
| MCP server (any) | 20% | 14% | +6 |
| MCP server (first-party) | 18% | 12% | +6 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 14% | 11% | +3 |
| Security | 98% | 98% | 0 |
| Arazzo workflows | 2% | 2% | 0 |
| Governance rules | 8% | 14% | -6 |
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.
- 1 CrowdStrike 67.1
- 2 AirMDR 55.1
- 3 Panther 54.6
- 4 Axonius 51.4
- 5 Picus Security 49.3
- 6 Cyware 49.2
- 7 Splunk SOAR 44.7
- 8 Vectra AI 43.2
- 9 Google Cloud Chronicle 43
- 10 Arctic Wolf 42.6
- 1 AirMDR 45.8
- 2 CrowdStrike 35.1
- 3 Cyware 32.4
- 4 Panther 30.8
- 5 Picus Security 27.8
- 6 Scanner 27.4
- 7 Axonius 25.8
- 8 Google Cloud Chronicle 24.8
- 9 Vectra AI 24.6
- 10 Anvilogic 23
Coverage caveat. 42 of 48 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 5 October 2026, across 29093 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.