Project
ProjectProjectsprojectprojects
Providers using this tag (549)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 10 Complete, well-documented, and agent-ready
Strong 69 Solid coverage with minor gaps
Developing 241 Usable, with meaningful gaps to close
Thin 194 Limited public surface area
Emerging 33 Early or largely undocumented
Minimal 2 Almost no public developer surface
APIs with this tag (572)
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 9 Complete, well-documented, and agent-ready
Strong 74 Solid coverage with minor gaps
Developing 245 Usable, with meaningful gaps to close
Thin 210 Limited public surface area
Emerging 32 Early or largely undocumented
Minimal 2 Almost no public developer surface
Score breakdown
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 549 providers in the APIs.io catalog tagged Project, 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 | 54.6 | 17.5 | +37.1 | 549 |
| Developer Ergonomics | 38.7 | 17.9 | +20.8 | 549 |
| Access Clarity | 40.2 | 22.3 | +17.9 | 549 |
| Operational Transparency | 28.7 | 11.3 | +17.4 | 549 |
| Discoverability | 72.2 | 60.4 | +11.8 | 549 |
| Contract Governance | 14.3 | 6.4 | +7.9 | 549 |
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) | 34% | 16% | +18 |
| MCP server (first-party) | 14% | 7% | +7 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 21% | 9% | +12 |
| Security | 99% | 88% | +11 |
| Arazzo workflows | 9% | 2% | +7 |
| Governance rules | 49% | 13% | +36 |
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 Adobe 80.4
- 2 Swetrix 78.6
- 3 Treasure Data 76.7
- 4 SendPulse 75.7
- 5 Optimizely 75.1
- 6 Bloomreach 73.7
- 7 Adobe Suite 71.2
- 8 Benchling 67.8
- 9 Notion 66.9
- 10 Asana 66.5
- 1 OpenGov 63.1
- 2 FLORA 62.4
- 3 Adobe Suite 61.5
- 4 Terabase Energy 60.6
- 5 Bria 58.9
- 6 GC AI 58.8
- 7 Bloomreach 58.5
- 8 Upsun 56.7
- 9 Sumble 56.3
- 10 SendPulse 55.8
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/project"
curl "https://apis.io/api/v1/tags?limit=25"
curl "https://apis.io/api/v1/cohorts/tag/project"
curl "https://apis.io/api/v1/cohorts/tag/project/stats" \
-H "X-API-Key: $APIS_IO_KEY"
Discovery needs no key. Ratings and market analysis are Pro.