Development
Providers using this tag (114)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 1 Complete, well-documented, and agent-ready
Strong 5 Solid coverage with minor gaps
Developing 9 Usable, with meaningful gaps to close
Thin 9 Limited public surface area
Emerging 6 Early or largely undocumented
Minimal 84 Almost no public developer surface
APIs with this tag (107)
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 2 Complete, well-documented, and agent-ready
Strong 3 Solid coverage with minor gaps
Developing 7 Usable, with meaningful gaps to close
Thin 5 Limited public surface area
Emerging 7 Early or largely undocumented
Minimal 83 Almost no public developer surface
Score breakdown
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 114 providers in the APIs.io catalog tagged Development, scored on the Kin Score. Every figure below is computed from the catalog — nothing here is written.
| Facet | This cohort | Catalog | Difference | Scored |
|---|---|---|---|---|
| Discoverability | 60.2 | 60.4 | -0.2 | 114 |
| Contract Governance | 5.3 | 6.4 | -1.1 | 114 |
| Operational Transparency | 7.7 | 11.3 | -3.6 | 114 |
| Contract Quality | 10.9 | 17.5 | -6.6 | 114 |
| Developer Ergonomics | 10.5 | 17.9 | -7.4 | 114 |
| Access Clarity | 12 | 22.3 | -10.3 | 114 |
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) | 7% | 16% | -9 |
| MCP server (first-party) | 4% | 7% | -3 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 8% | 9% | -1 |
| Security | 87% | 88% | -1 |
| Arazzo workflows | 5% | 2% | +3 |
| Governance rules | 18% | 13% | +5 |
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 Figma 63.8
- 3 WebScraping.AI 62.6
- 4 IPinfo 61.9
- 5 Databricks 59.1
- 6 Atlassian 54.7
- 7 Microsoft Endpoint Configuration Management 53.5
- 8 Salesforce Automation 51.6
- 9 SnapLogic 49
- 10 Azure DevTest Labs 46.7
- 1 WebScraping.AI 65
- 2 Figma 53.2
- 3 Salesforce 52.2
- 4 Atlassian 41.9
- 5 Databricks 40.1
- 6 IPinfo 33.8
- 7 Amazon Cloud9 30.2
- 8 Salesforce Automation 26.1
- 9 ipify 25.8
- 10 ReqRes 25.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/development"
curl "https://apis.io/api/v1/tags?limit=25"
curl "https://apis.io/api/v1/cohorts/tag/development"
curl "https://apis.io/api/v1/cohorts/tag/development/stats" \
-H "X-API-Key: $APIS_IO_KEY"
Discovery needs no key. Ratings and market analysis are Pro.