Repository
Repositoryrepository
Providers using this tag (179)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 2 Complete, well-documented, and agent-ready
Strong 11 Solid coverage with minor gaps
Developing 37 Usable, with meaningful gaps to close
Thin 55 Limited public surface area
Emerging 66 Early or largely undocumented
Minimal 8 Almost no public developer surface
APIs with this tag (198)
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 1 Complete, well-documented, and agent-ready
Strong 10 Solid coverage with minor gaps
Developing 32 Usable, with meaningful gaps to close
Thin 61 Limited public surface area
Emerging 94 Early or largely undocumented
Score breakdown
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 179 providers in the APIs.io catalog tagged Repository, 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 | 37.2 | 17.5 | +19.7 | 179 |
| Operational Transparency | 25.1 | 11.3 | +13.8 | 179 |
| Access Clarity | 31.4 | 22.3 | +9.1 | 179 |
| Discoverability | 66.7 | 60.4 | +6.3 | 179 |
| Contract Governance | 10.2 | 6.4 | +3.8 | 179 |
| Developer Ergonomics | 17 | 17.9 | -0.9 | 179 |
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) | 8% | 16% | -8 |
| MCP server (first-party) | 5% | 7% | -2 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 21% | 9% | +12 |
| Security | 94% | 88% | +6 |
| Arazzo workflows | 3% | 2% | +1 |
| Governance rules | 51% | 13% | +38 |
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 Cisco Identity Services Engine 67.8
- 2 Oracle Siebel 67.1
- 3 Gitea 65.5
- 4 Palo Alto Networks 63.7
- 5 Delft University of Technology 62.4
- 6 Unified.to 60.4
- 7 Red Hat 59.1
- 8 University of Warwick 58.3
- 9 Amazon CodeArtifact 57.9
- 10 University of Michigan-Ann Arbor 57.9
- 1 Sageox 63.8
- 2 Upsun 56.7
- 3 Red Hat 52.3
- 4 Kubeshop 50
- 5 Anaconda 41.4
- 6 Spree Commerce 41.4
- 7 Palo Alto Networks 39.4
- 8 Replicas 39.4
- 9 Cisco Identity Services Engine 36.2
- 10 JFrog Artifactory 33.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/repository"
curl "https://apis.io/api/v1/tags?limit=25"
curl "https://apis.io/api/v1/cohorts/tag/repository"
curl "https://apis.io/api/v1/cohorts/tag/repository/stats" \
-H "X-API-Key: $APIS_IO_KEY"
Discovery needs no key. Ratings and market analysis are Pro.