Credentials
Credentialscredentials
Providers using this tag (93)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 6 Complete, well-documented, and agent-ready
Strong 20 Solid coverage with minor gaps
Developing 38 Usable, with meaningful gaps to close
Thin 22 Limited public surface area
Emerging 5 Early or largely undocumented
Minimal 2 Almost no public developer surface
APIs with this tag (95)
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 5 Complete, well-documented, and agent-ready
Strong 23 Solid coverage with minor gaps
Developing 37 Usable, with meaningful gaps to close
Thin 24 Limited public surface area
Emerging 6 Early or largely undocumented
Score breakdown
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 93 providers in the APIs.io catalog tagged Credentials, 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.6 | 17.5 | +40.1 | 93 |
| Developer Ergonomics | 47.1 | 17.9 | +29.2 | 93 |
| Operational Transparency | 31.8 | 11.3 | +20.5 | 93 |
| Access Clarity | 41.9 | 22.3 | +19.6 | 93 |
| Discoverability | 72.1 | 60.4 | +11.7 | 93 |
| Contract Governance | 17.9 | 6.4 | +11.5 | 93 |
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) | 43% | 16% | +27 |
| MCP server (first-party) | 17% | 7% | +10 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 27% | 9% | +18 |
| Security | 98% | 88% | +10 |
| Arazzo workflows | 19% | 2% | +17 |
| Governance rules | 53% | 13% | +40 |
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 Twilio 73.4
- 3 Dynatrace 71.8
- 4 ThousandEyes 70.2
- 5 Zocdoc 69.7
- 6 Amazon Secrets Manager 67.4
- 7 Logz.io 65.2
- 8 Reputation 64.5
- 9 Palo Alto Networks 63.7
- 10 IBM 62.6
- 1 Duvo Ai 63.1
- 2 duvo.ai 60.4
- 3 Red Hat 52.3
- 4 Salesforce 52.2
- 5 Shift4 51.4
- 6 ThousandEyes 51.1
- 7 Boxc 50.1
- 8 Zocdoc 49
- 9 Customers Bank 48.4
- 10 GitHub 45.5
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/credentials"
curl "https://apis.io/api/v1/tags?limit=25"
curl "https://apis.io/api/v1/cohorts/tag/credentials"
curl "https://apis.io/api/v1/cohorts/tag/credentials/stats" \
-H "X-API-Key: $APIS_IO_KEY"
Discovery needs no key. Ratings and market analysis are Pro.