Foundation Models
Foundation Modelsfoundation-models
Providers using this tag (107)
Ranked by API Evangelist rating — Exemplar and Strong are expanded by default.
Exemplar 2 Complete, well-documented, and agent-ready
Strong 5 Solid coverage with minor gaps
Developing 7 Usable, with meaningful gaps to close
Thin 16 Limited public surface area
Emerging 23 Early or largely undocumented
Minimal 54 Almost no public developer surface
APIs with this tag (12)
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 →
Strong 5 Solid coverage with minor gaps
Developing 2 Usable, with meaningful gaps to close
Thin 2 Limited public surface area
Emerging 3 Early or largely undocumented
Score breakdown
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 107 providers in the APIs.io catalog tagged Foundation Models, scored on the Kin Score. Every figure below is computed from the catalog — nothing here is written.
| Facet | This cohort | Catalog | Difference | Scored |
|---|---|---|---|---|
| Developer Ergonomics | 18.7 | 17.9 | +0.8 | 107 |
| Operational Transparency | 10.4 | 11.3 | -0.9 | 107 |
| Discoverability | 59.4 | 60.4 | -1 | 107 |
| Contract Quality | 14.7 | 17.5 | -2.8 | 107 |
| Contract Governance | 3.6 | 6.4 | -2.8 | 107 |
| Access Clarity | 18.6 | 22.3 | -3.7 | 107 |
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) | 12% | 16% | -4 |
| MCP server (first-party) | 7% | 7% | 0 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 5% | 9% | -4 |
| Security | 93% | 88% | +5 |
| Arazzo workflows | 3% | 2% | +1 |
| Governance rules | 13% | 13% | 0 |
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 NVIDIA NIM 71.2
- 2 Anthropic 68.6
- 3 IBM 62.6
- 4 Recraft 60.7
- 5 Amazon Web Services (AWS) 60.6
- 6 Amazon Bedrock 56.4
- 7 Prime Intellect 55.1
- 8 Uthana 50.7
- 9 Scale AI 47.6
- 10 Prior Labs 45.9
- 1 IBM 39.4
- 2 Anthropic 38.1
- 3 Prior Labs 37.6
- 4 Together AI 33.5
- 5 Strand AI 30.7
- 6 Inflection AI 30.6
- 7 NVIDIA NIM 28.8
- 8 Forithmus 27.8
- 9 Prime Intellect 27.3
- 10 xAI 25.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/foundation-models"
curl "https://apis.io/api/v1/tags?limit=25"
curl "https://apis.io/api/v1/cohorts/tag/foundation-models"
curl "https://apis.io/api/v1/cohorts/tag/foundation-models/stats" \
-H "X-API-Key: $APIS_IO_KEY"
Discovery needs no key. Ratings and market analysis are Pro.