OpenAI-Compatible
OpenAI CompatibleOpenAI compatibleOpenAI-CompatibleOpenAI-compatibleopenai-compatible
Providers using this tag (59)
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 19 Usable, with meaningful gaps to close
Thin 29 Limited public surface area
Emerging 5 Early or largely undocumented
APIs with this tag (37)
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 3 Complete, well-documented, and agent-ready
Strong 3 Solid coverage with minor gaps
Developing 7 Usable, with meaningful gaps to close
Thin 17 Limited public surface area
Emerging 5 Early or largely undocumented
Minimal 2 Almost no public developer surface
Score breakdown
Related tags
Where this tag comes from
Cohort brief
Auto-generatedThe 59 providers in the APIs.io catalog tagged OpenAI-Compatible, 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 | 42.2 | 17.9 | +24.3 | 59 |
| Contract Quality | 40.8 | 17.5 | +23.3 | 59 |
| Discoverability | 75.4 | 60.4 | +15 | 59 |
| Access Clarity | 34.8 | 22.3 | +12.5 | 59 |
| Operational Transparency | 22.7 | 11.3 | +11.4 | 59 |
| Contract Governance | 11 | 6.4 | +4.6 | 59 |
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) | 7% | 7% | 0 |
| Agent Skills | 0% | 0% | 0 |
| OAuth scopes | 0% | 9% | -9 |
| Security | 98% | 88% | +10 |
| Arazzo workflows | 7% | 2% | +5 |
| Governance rules | 22% | 13% | +9 |
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 Cloudflare 62
- 3 Crusoe 60.6
- 4 Prime Intellect 55.1
- 5 Inference 53.9
- 6 RightNow AI 53.5
- 7 0G Labs 51.2
- 8 Lambda 50.9
- 9 OpenRelay 50.8
- 10 FriendliAI 49.9
- 1 Cloudflare 44.5
- 2 OpenRelay 40.6
- 3 Crusoe 40.3
- 4 RouterPlex 37.2
- 5 Textcortex 37.2
- 6 Bifrost 34.9
- 7 FriendliAI 31.5
- 8 Inference 30.9
- 9 Kimi (Moonshot AI) 30.9
- 10 0G Labs 30.6
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/openai-compatible"
curl "https://apis.io/api/v1/tags?limit=25"
curl "https://apis.io/api/v1/cohorts/tag/openai-compatible"
curl "https://apis.io/api/v1/cohorts/tag/openai-compatible/stats" \
-H "X-API-Key: $APIS_IO_KEY"
Discovery needs no key. Ratings and market analysis are Pro.