Settings
Settingssettings
Providers using this tag (148)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 6 Complete, well-documented, and agent-ready
Strong 24 Solid coverage with minor gaps
Developing 55 Usable, with meaningful gaps to close
Thin 49 Limited public surface area
APIs with this tag (156)
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 10 Complete, well-documented, and agent-ready
Strong 25 Solid coverage with minor gaps
Developing 57 Usable, with meaningful gaps to close
Thin 50 Limited public surface area
Emerging 14 Early or largely undocumented
Score breakdown
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 148 providers in the APIs.io catalog tagged Settings, 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 | 53.5 | 17.5 | +36 | 148 |
| Developer Ergonomics | 42 | 17.9 | +24.1 | 148 |
| Operational Transparency | 29.2 | 11.3 | +17.9 | 148 |
| Access Clarity | 37.4 | 22.3 | +15.1 | 148 |
| Discoverability | 73.2 | 60.4 | +12.8 | 148 |
| Contract Governance | 18.3 | 6.4 | +11.9 | 148 |
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) | 46% | 16% | +30 |
| MCP server (first-party) | 20% | 7% | +13 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 32% | 9% | +23 |
| Security | 99% | 88% | +11 |
| Arazzo workflows | 16% | 2% | +14 |
| Governance rules | 45% | 13% | +32 |
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 Salesforce 83.3
- 2 HubSpot 82.4
- 3 Twilio 73.4
- 4 Dynatrace 71.8
- 5 Metriport 68.2
- 6 Fitbit 67.6
- 7 Gitea 65.5
- 8 DoiT 64.7
- 9 Cisco Catalyst SD-WAN 64.6
- 10 Amigo 63.8
- 1 DoiT 74.4
- 2 Automattic 62.3
- 3 Sarj AI Developer API 60.4
- 4 Extole 57.2
- 5 Genesys 55.1
- 6 HubSpot 54.4
- 7 Campfire 54.1
- 8 Salesforce 52.2
- 9 IRONSCALES 51.6
- 10 Confluence 50
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/settings"
curl "https://apis.io/api/v1/tags?limit=25"
curl "https://apis.io/api/v1/cohorts/tag/settings"
curl "https://apis.io/api/v1/cohorts/tag/settings/stats" \
-H "X-API-Key: $APIS_IO_KEY"
Discovery needs no key. Ratings and market analysis are Pro.