Dashboards
Dashboardsdashboards
Providers using this tag (138)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 5 Complete, well-documented, and agent-ready
Strong 25 Solid coverage with minor gaps
Developing 54 Usable, with meaningful gaps to close
Thin 34 Limited public surface area
Emerging 18 Early or largely undocumented
Minimal 2 Almost no public developer surface
APIs with this tag (112)
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 7 Complete, well-documented, and agent-ready
Strong 28 Solid coverage with minor gaps
Developing 43 Usable, with meaningful gaps to close
Thin 27 Limited public surface area
Emerging 6 Early or largely undocumented
Minimal 1 Almost no public developer surface
Score breakdown
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 138 providers in the APIs.io catalog tagged Dashboards, 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 | 47 | 17.5 | +29.5 | 138 |
| Developer Ergonomics | 44.3 | 17.9 | +26.4 | 138 |
| Access Clarity | 43.8 | 22.3 | +21.5 | 138 |
| Operational Transparency | 29.5 | 11.3 | +18.2 | 138 |
| Discoverability | 69.4 | 60.4 | +9 | 138 |
| Contract Governance | 15.3 | 6.4 | +8.9 | 138 |
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) | 39% | 16% | +23 |
| MCP server (first-party) | 19% | 7% | +12 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 20% | 9% | +11 |
| Security | 98% | 88% | +10 |
| Arazzo workflows | 14% | 2% | +12 |
| Governance rules | 43% | 13% | +30 |
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 MoEngage 75.8
- 3 Dynatrace 71.8
- 4 ThousandEyes 70.2
- 5 Matomo 67.3
- 6 Logz.io 65.2
- 7 ServiceNow 64.8
- 8 Syllable 64.8
- 9 Amigo 63.8
- 10 Adafruit IO 63.3
- 1 Automattic 62.3
- 2 MoEngage 59.4
- 3 Equals 54.4
- 4 Salesforce 52.2
- 5 ThousandEyes 51.1
- 6 Sentry 44.6
- 7 Coval 43.6
- 8 Amigo 43.5
- 9 Atlassian 41.9
- 10 Kibana 41.7
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/dashboards"
curl "https://apis.io/api/v1/tags?limit=25"
curl "https://apis.io/api/v1/cohorts/tag/dashboards"
curl "https://apis.io/api/v1/cohorts/tag/dashboards/stats" \
-H "X-API-Key: $APIS_IO_KEY"
Discovery needs no key. Ratings and market analysis are Pro.