Legacy
Legacylegacy
Providers using this tag (117)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 10 Complete, well-documented, and agent-ready
Strong 24 Solid coverage with minor gaps
Developing 25 Usable, with meaningful gaps to close
Thin 22 Limited public surface area
Emerging 19 Early or largely undocumented
APIs with this tag (115)
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 12 Complete, well-documented, and agent-ready
Strong 23 Solid coverage with minor gaps
Developing 26 Usable, with meaningful gaps to close
Thin 25 Limited public surface area
Emerging 27 Early or largely undocumented
Minimal 2 Almost no public developer surface
Score breakdown
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 117 providers in the APIs.io catalog tagged Legacy, 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 | 40.7 | 17.5 | +23.2 | 117 |
| Developer Ergonomics | 35.7 | 17.9 | +17.8 | 117 |
| Operational Transparency | 28.3 | 11.3 | +17 | 117 |
| Access Clarity | 38.9 | 22.3 | +16.6 | 117 |
| Contract Governance | 20.4 | 6.4 | +14 | 117 |
| Discoverability | 69.8 | 60.4 | +9.4 | 117 |
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) | 13% | 7% | +6 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 25% | 9% | +16 |
| Security | 91% | 88% | +3 |
| Arazzo workflows | 16% | 2% | +14 |
| Governance rules | 44% | 13% | +31 |
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 Marketing Cloud 83.5
- 2 Salesforce 83.3
- 3 MailerLite 77.2
- 4 Vessel 72.1
- 5 Jefferson Health 71.1
- 6 Kraken 70.6
- 7 Plaid 68.2
- 8 Adobe Analytics 67.4
- 9 ActiveCampaign 67.2
- 10 Enrich 66.9
- 1 Adobe Analytics 66.5
- 2 S&P Global 63.7
- 3 EGYM 57.7
- 4 Salesforce Marketing Cloud 56.2
- 5 Bluecore 54.1
- 6 Jira 52.9
- 7 Salesforce 52.2
- 8 MailerLite 49.1
- 9 Decisiv 49
- 10 ActiveCampaign 47.9
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/legacy"
curl "https://apis.io/api/v1/tags?limit=25"
curl "https://apis.io/api/v1/cohorts/tag/legacy"
curl "https://apis.io/api/v1/cohorts/tag/legacy/stats" \
-H "X-API-Key: $APIS_IO_KEY"
Discovery needs no key. Ratings and market analysis are Pro.