Content Moderation
Providers using this tag (27)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Strong 5 Solid coverage with minor gaps
Developing 12 Usable, with meaningful gaps to close
Thin 3 Limited public surface area
Minimal 5 Almost no public developer surface
APIs with this tag (5)
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 →
Strong 1 Solid coverage with minor gaps
Developing 3 Usable, with meaningful gaps to close
Thin 1 Limited public surface area
Companies reaching this through an API (3)
These companies publish an API, specification or operation carrying “Content Moderation” 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 27 providers in the APIs.io catalog tagged Content Moderation, 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 | 43.6 | 23.2 | +20.4 | 27 |
| Contract Quality | 34.2 | 17.6 | +16.6 | 27 |
| Access Clarity | 38 | 26.5 | +11.5 | 27 |
| Discoverability | 66.1 | 58.1 | +8 | 27 |
| Operational Transparency | 21 | 13.7 | +7.3 | 27 |
| Contract Governance | 10.6 | 6.3 | +4.3 | 27 |
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) | 22% | 14% | +8 |
| MCP server (first-party) | 22% | 12% | +10 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 7% | 11% | -4 |
| Security | 100% | 98% | +2 |
| Arazzo workflows | 7% | 2% | +5 |
| Governance rules | 11% | 14% | -3 |
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 Refuel 61.6
- 2 Amazon Rekognition 55.7
- 3 Modulate 55.7
- 4 BudgetPixel 54.3
- 5 Vettly 53.3
- 6 ActiveFence 51.7
- 7 TypeSafe AI 51.6
- 8 MediaRuntime 49.6
- 9 GPTZero 49.2
- 10 SafetyKit 47.6
- 1 BudgetPixel 55.3
- 2 Vettly 43.2
- 3 TypeSafe AI 37.8
- 4 MediaRuntime 37.2
- 5 Amazon Rekognition 34
- 6 Memories 33.1
- 7 Refuel 32.2
- 8 AnyImageDetector 32.2
- 9 Modulate 30.8
- 10 Respondology 29.3
Coverage caveat. 22 of 27 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.