Entitlements
Entitlementsentitlements
Providers using this tag (42)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Strong 7 Solid coverage with minor gaps
Developing 17 Usable, with meaningful gaps to close
Thin 8 Limited public surface area
Emerging 6 Early or largely undocumented
Minimal 1 Almost no public developer surface
APIs with this tag (35)
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 7 Solid coverage with minor gaps
Developing 14 Usable, with meaningful gaps to close
Thin 5 Limited public surface area
Emerging 7 Early or largely undocumented
Score breakdown
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 42 providers in the APIs.io catalog tagged Entitlements, scored on the Kin Score. Every figure below is computed from the catalog — nothing here is written.
| Facet | This cohort | Catalog | Difference | Scored |
|---|---|---|---|---|
| Contract Quality | 51.9 | 17.5 | +34.4 | 42 |
| Developer Ergonomics | 39.7 | 17.9 | +21.8 | 42 |
| Operational Transparency | 31.1 | 11.3 | +19.8 | 42 |
| Access Clarity | 39.4 | 22.3 | +17.1 | 42 |
| Contract Governance | 18.4 | 6.4 | +12 | 42 |
| Discoverability | 71.7 | 60.4 | +11.3 | 42 |
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) | 31% | 16% | +15 |
| MCP server (first-party) | 19% | 7% | +12 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 24% | 9% | +15 |
| Security | 98% | 88% | +10 |
| Arazzo workflows | 14% | 2% | +12 |
| Governance rules | 52% | 13% | +39 |
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.
Work with this as data
Every tag here is available over the APIs.io API and to AI agents over MCP.