Identifiers
Identifiersidentifiers
Providers using this tag (34)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 3 Complete, well-documented, and agent-ready
Strong 10 Solid coverage with minor gaps
Developing 4 Usable, with meaningful gaps to close
Thin 9 Limited public surface area
APIs with this tag (34)
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 3 Complete, well-documented, and agent-ready
Strong 10 Solid coverage with minor gaps
Developing 6 Usable, with meaningful gaps to close
Thin 7 Limited public surface area
Emerging 8 Early or largely undocumented
Score breakdown
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 34 providers in the APIs.io catalog tagged Identifiers, 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.9 | 17.5 | +36.4 | 34 |
| Developer Ergonomics | 39.7 | 17.9 | +21.8 | 34 |
| Operational Transparency | 32.5 | 11.3 | +21.2 | 34 |
| Contract Governance | 19.5 | 6.4 | +13.1 | 34 |
| Access Clarity | 35 | 22.3 | +12.7 | 34 |
| Discoverability | 68.9 | 60.4 | +8.5 | 34 |
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) | 32% | 16% | +16 |
| MCP server (first-party) | 12% | 7% | +5 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 29% | 9% | +20 |
| Security | 97% | 88% | +9 |
| Arazzo workflows | 26% | 2% | +24 |
| Governance rules | 56% | 13% | +43 |
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 Stripe 83.2
- 3 New Relic 68.8
- 4 Factset 64.8
- 5 Ordnance Survey 62.6
- 6 GitHub 62.4
- 7 Factiva 61.9
- 8 Zaius 61.7
- 9 Shopify 60.4
- 10 Datadog 57.1
- 1 Factset 52.8
- 2 Salesforce 52.2
- 3 Stripe 47.8
- 4 GitHub 45.5
- 5 Factiva 43.3
- 6 Atlassian 41.9
- 7 Shopify 40.6
- 8 Datadog 38.3
- 9 U.S. Geological Survey 35.4
- 10 Ordnance Survey 34
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/identifiers"
curl "https://apis.io/api/v1/tags?limit=25"
curl "https://apis.io/api/v1/cohorts/tag/identifiers"
curl "https://apis.io/api/v1/cohorts/tag/identifiers/stats" \
-H "X-API-Key: $APIS_IO_KEY"
Discovery needs no key. Ratings and market analysis are Pro.