Translation
Providers using this tag (71)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 1 Complete, well-documented, and agent-ready
Strong 3 Solid coverage with minor gaps
Developing 32 Usable, with meaningful gaps to close
Thin 24 Limited public surface area
Emerging 5 Early or largely undocumented
Minimal 6 Almost no public developer surface
APIs with this tag (33)
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 2 Solid coverage with minor gaps
Developing 18 Usable, with meaningful gaps to close
Thin 8 Limited public surface area
Emerging 4 Early or largely undocumented
Score breakdown
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 71 providers in the APIs.io catalog tagged Translation, 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 | 45.4 | 17.5 | +27.9 | 71 |
| Access Clarity | 39.4 | 22.3 | +17.1 | 71 |
| Developer Ergonomics | 33.3 | 17.9 | +15.4 | 71 |
| Operational Transparency | 26.5 | 11.3 | +15.2 | 71 |
| Discoverability | 71.6 | 60.4 | +11.2 | 71 |
| Contract Governance | 9.6 | 6.4 | +3.2 | 71 |
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) | 27% | 16% | +11 |
| MCP server (first-party) | 10% | 7% | +3 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 10% | 9% | +1 |
| Security | 99% | 88% | +11 |
| Arazzo workflows | 1% | 2% | -1 |
| Governance rules | 27% | 13% | +14 |
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 Suite 71.2
- 2 General Translation 64.7
- 3 Lilt 61.9
- 4 Rigetti Computing 57.2
- 5 Onshape 52.9
- 6 Gladia 52.1
- 7 Smartcat 51.6
- 8 SuprSend 51.3
- 9 Defacto 50.9
- 10 Sarvam 50.4
- 1 Adobe Suite 61.5
- 2 Lilt 49.8
- 3 Rapidata 41.7
- 4 Google 39.2
- 5 Bluejay 38.6
- 6 Algebras AI Inc. 37.4
- 7 Weblate 37.4
- 8 Onshape 37.2
- 9 TextMaster 37.2
- 10 SuprSend 33
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/translation"
curl "https://apis.io/api/v1/tags?limit=25"
curl "https://apis.io/api/v1/cohorts/tag/translation"
curl "https://apis.io/api/v1/cohorts/tag/translation/stats" \
-H "X-API-Key: $APIS_IO_KEY"
Discovery needs no key. Ratings and market analysis are Pro.