Governance
Providers using this tag (125)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 1 Complete, well-documented, and agent-ready
Strong 5 Solid coverage with minor gaps
Developing 21 Usable, with meaningful gaps to close
Thin 25 Limited public surface area
Emerging 39 Early or largely undocumented
Minimal 31 Almost no public developer surface
Unrated 3 Not yet scored
APIs with this tag (87)
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 11 Complete, well-documented, and agent-ready
Strong 29 Solid coverage with minor gaps
Developing 17 Usable, with meaningful gaps to close
Thin 21 Limited public surface area
Emerging 8 Early or largely undocumented
Minimal 1 Almost no public developer surface
Companies reaching this through an API (56)
These companies publish an API, specification or operation carrying “Governance” 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 56 companies ↓
Score breakdown
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 114 providers in the APIs.io catalog tagged Governance, 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 | 26.9 | 23.4 | +3.5 | 114 |
| Access Clarity | 29.8 | 26.5 | +3.3 | 114 |
| Contract Governance | 8.2 | 6.5 | +1.7 | 114 |
| Discoverability | 62.1 | 61 | +1.1 | 114 |
| Operational Transparency | 15 | 14 | +1 | 114 |
| Contract Quality | 21 | 20.1 | +0.9 | 114 |
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) | 13% | 10% | +3 |
| MCP server (first-party) | 15% | 13% | +2 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 9% | 11% | -2 |
| Security | 97% | 96% | +1 |
| Arazzo workflows | 4% | 2% | +2 |
| Governance rules | 20% | 13% | +7 |
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 Redocly 75.5
- 2 anecdotes 63.1
- 3 Eclipse Foundation 59.5
- 4 Treblle 55.8
- 5 Amazon Config 55.2
- 6 Amazon CloudTrail 54.3
- 7 Amazon Organizations 53.2
- 8 Sweep 51.6
- 9 Portkey 50.3
- 10 Amazon Backup 49.8
- 1 Clawvisor 55.8
- 2 Goethena 53.4
- 3 Sweep 48.5
- 4 Eclipse Foundation 48.4
- 5 anecdotes 36.7
- 6 Portkey 36
- 7 Idle Finance 35.4
- 8 Accept 34
- 9 Vanta 33.8
- 10 Redocly 33.1
Work with this as data
Every tag here is available over the APIs.io API and to AI agents over MCP.