Security
Securitysecurity
Providers using this tag (818)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 8 Complete, well-documented, and agent-ready
Strong 56 Solid coverage with minor gaps
Developing 174 Usable, with meaningful gaps to close
Thin 153 Limited public surface area
Emerging 206 Early or largely undocumented
Minimal 199 Almost no public developer surface
APIs with this tag (517)
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 46 Complete, well-documented, and agent-ready
Strong 145 Solid coverage with minor gaps
Developing 126 Usable, with meaningful gaps to close
Thin 104 Limited public surface area
Emerging 59 Early or largely undocumented
Minimal 37 Almost no public developer surface
Companies reaching this through an API (200)
These companies publish an API, specification or operation carrying “Security” 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.
Show all 200 companies ↓
Score breakdown
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 730 providers in the APIs.io catalog tagged Security, scored on the Kin Score. Every figure below is computed from the catalog — nothing here is written.
| Facet | This cohort | Catalog | Difference | Scored |
|---|---|---|---|---|
| Developer Ergonomics | 32.3 | 23.4 | +8.9 | 730 |
| Contract Quality | 25.2 | 19.8 | +5.4 | 730 |
| Operational Transparency | 19 | 13.9 | +5.1 | 730 |
| Access Clarity | 31.3 | 26.5 | +4.8 | 730 |
| Discoverability | 64.2 | 61.2 | +3 | 730 |
| Contract Governance | 9.4 | 6.4 | +3 | 730 |
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) | 14% | 10% | +4 |
| MCP server (first-party) | 16% | 13% | +3 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 11% | 11% | 0 |
| Security | 97% | 96% | +1 |
| Arazzo workflows | 5% | 2% | +3 |
| Governance rules | 19% | 14% | +5 |
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 Elastic Stack (ELK Stack) 76.7
- 2 Amazon VPN 73.3
- 3 Mailboxlayer 71.9
- 4 Aembit 71.5
- 5 Paubox 71.5
- 6 Snyk 71.3
- 7 OneTrust 68.2
- 8 Shodan 67.2
- 9 Clerk 65.8
- 10 Strivacity 65.7
- 1 Paubox 61.5
- 2 Clearspeed 58.1
- 3 Aembit 57.2
- 4 Huntress 55.6
- 5 Clawvisor 52.2
- 6 OneTrust 51.6
- 7 Cloudflare 49.6
- 8 Elastic Stack (ELK Stack) 48.8
- 9 F5 48.7
- 10 Drata 48.6
Work with this as data
Every tag here is available over the APIs.io API and to AI agents over MCP.