niche · -0.9 capability action

API Security

Score 18.8 / 100 54 providers +6 via APIs 23 APIs Search apis.io →

Providers using this tag (54)

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

Exemplar 2 Complete, well-documented, and agent-ready
Strong 3 Solid coverage with minor gaps
Developing 6 Usable, with meaningful gaps to close
Thin 19 Limited public surface area
Emerging 15 Early or largely undocumented
Minimal 8 Almost no public developer surface
Unrated 1 Not yet scored

APIs with this tag (22)

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 2 Complete, well-documented, and agent-ready
Strong 1 Solid coverage with minor gaps
Developing 3 Usable, with meaningful gaps to close
Thin 8 Limited public surface area
Emerging 4 Early or largely undocumented
Minimal 4 Almost no public developer surface

Companies reaching this through an API (6)

These companies publish an API, specification or operation carrying “API 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.

APIs.io Engineering Platform Cloudflare CloudGuard IBM Postman Rhapsody

Score breakdown

Frequency
47.7
log-scaled weighted occurrences
Breadth
0.7
spread across providers
Quality lift
28.8
mean composite of providers using it
Cohesion
6.4
strength of nearest seed neighbor

Related tags

DAST 11 co-occurrences API Discovery 10 co-occurrences Application Security 14 co-occurrences Web Application Firewall 6 co-occurrences WAF 6 co-occurrences API Governance 5 co-occurrences Vulnerability Scanning 5 co-occurrences API Testing 6 co-occurrences

Where this tag comes from

Provider tag54
Api tag23
Openapi tag1
Openapi op tag1

Cohort brief

Auto-generated

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

Providers
50
of 54 in the catalog
Mean Kin Score
29.2
+5.1 vs catalog 24.1
Mean Agent Readiness
15.1
+1.0 vs catalog 14.1
Spread
4.7–67.7
median 27 · σ 16.3
How the 50 split by band
Exemplar 2Strong 3Developing 6Thin 17Emerging 15Minimal 7
Facet averages, against the whole catalog
FacetThis cohortCatalogDifferenceScored
Developer Ergonomics 32 24.5 +7.5 50
Contract Governance 14.9 9.7 +5.2 50
Operational Transparency 18 13.2 +4.8 50
Discoverability 63.8 59.1 +4.7 50
Contract Quality 22.6 18.6 +4 50
Access Clarity 33 30 +3 50

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) 16% 18% -2
MCP server (first-party) 12% 16% -4
Agent Skills 0% 0% 0
OAuth scopes 6% 13% -7
Security 98% 99% -1
Arazzo workflows 2% 1% +1
Governance rules 51% 36% +15

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 Routebase 67.7
  2. 2 Treblle 67.4
  3. 3 Authlete 60.1
  4. 4 detectify 57.8
  5. 5 Pynt 55.1
  6. 6 CyCognito 53.2
  7. 7 Upwind 52.3
  8. 8 Apinizer 48.5
  9. 9 Gray Swan 46.1
  10. 10 StackHawk 45.7
Top by Agent Readiness
  1. 1 Routebase 52.8
  2. 2 Upwind 40.3
  3. 3 CyCognito 38.6
  4. 4 Cequence Security 33.6
  5. 5 Authlete 30.8
  6. 6 APIClarity 30.7
  7. 7 Wallarm 30.2
  8. 8 Traceable 28.3
  9. 9 Akamai API Security 27.9
  10. 10 Chaitin Tech 26.8
All 54 members of this roster resolve to a provider in the catalog; 50 carry a score (93%). The figures above describe the scored members only.
Coverage caveat. 40 of 50 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 14 November 2026, across 41591 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/api-security"
All tags
curl "https://apis.io/api/v1/tags?limit=25"
As a scored cohort (paid plan)
The distribution (Pro)

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

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.