Permissions
Permissionspermissions
Providers using this tag (115)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 6 Complete, well-documented, and agent-ready
Strong 31 Solid coverage with minor gaps
Developing 45 Usable, with meaningful gaps to close
Thin 27 Limited public surface area
Emerging 6 Early or largely undocumented
APIs with this tag (119)
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 6 Complete, well-documented, and agent-ready
Strong 40 Solid coverage with minor gaps
Developing 41 Usable, with meaningful gaps to close
Thin 26 Limited public surface area
Emerging 6 Early or largely undocumented
Score breakdown
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 115 providers in the APIs.io catalog tagged Permissions, 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 | 57.8 | 17.5 | +40.3 | 115 |
| Developer Ergonomics | 48.6 | 17.9 | +30.7 | 115 |
| Operational Transparency | 36.3 | 11.3 | +25 | 115 |
| Access Clarity | 43.3 | 22.3 | +21 | 115 |
| Discoverability | 72.5 | 60.4 | +12.1 | 115 |
| Contract Governance | 17.4 | 6.4 | +11 | 115 |
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) | 52% | 16% | +36 |
| MCP server (first-party) | 19% | 7% | +12 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 36% | 9% | +27 |
| Security | 100% | 88% | +12 |
| Arazzo workflows | 23% | 2% | +21 |
| Governance rules | 48% | 13% | +35 |
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 Optimizely 75.1
- 2 Commerce Layer 72.4
- 3 Dynatrace 71.8
- 4 ThousandEyes 70.2
- 5 Matomo 67.3
- 6 Airbyte 66.6
- 7 Showpad 66.2
- 8 Syllable 64.8
- 9 Affinda 64.7
- 10 Coda Project 64.2
- 1 Insforge 59.9
- 2 nCino 56.7
- 3 Coda Project 55.5
- 4 ThousandEyes 51.1
- 5 Confluence 50
- 6 Showpad 48.2
- 7 H2O.ai 46.9
- 8 GitHub 45.5
- 9 Airbyte 43.9
- 10 Atlassian 41.9
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.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/tags/permissions"
curl "https://apis.io/api/v1/tags?limit=25"
curl "https://apis.io/api/v1/cohorts/tag/permissions"
curl "https://apis.io/api/v1/cohorts/tag/permissions/stats" \
-H "X-API-Key: $APIS_IO_KEY"
Discovery needs no key. Ratings and market analysis are Pro.