API Commons · Models · de facto

The OpenAI Interface

211 providers in the API Evangelist catalog state OpenAI compatibility. 120 of them publish an OpenAPI harvested byte-identical from their own site, and those are the denominator. A provider may implement an operation without publishing a spec, so these shares are a floor.

338operations graded
2core tier
19extended
317vendor only
175adopters recorded

How it was measured

Tiers are measured against what adopters publish, not asserted. Each METHOD and path is graded by the share of the publishing cohort that declares it. Grading by path alone credits every method on a path equally, which is wrong: GET and POST on /chat/completions are not implemented at the same rate.

The core tier

What a provider has to implement before a compatibility claim means anything. Every placement is measured, and the evidence for each sits in the tier profile.

POSTGET

Adopters

EvidenceCountWhat it means
declared101Publishes a machine-readable spec declaring them.
prose74Says so, and publishes nothing a reader can check.

Every entry in the registry carries the URL it was read from and the date it was read. A claim is never promoted to a verdict.

Providers that reach a tier

67 of the 175 recorded adopters demonstrably reach the core tier or better. The 24 below link to their catalog pages; the registry and matrix carry the rest.

.txt0G LabsAIMLAPIAleph AlphaCentMLCerebras SystemsCometAPIDeepInfraDeepSeekEden AIEdgeeEnvoyFeatherless AIFlexAIGroqHugging FaceHyperbolicHyperbolicKimi (Moonshot AI)LangDBMistral AIMoonshot AIMultiverse ComputingNexGen Cloud

Artifacts

Everything this standard publishes. All of it is generated from the profile, so a re-measurement moves every artifact together.

Source

OriginatorOpenAI
Read fromhttps://github.com/openai/openai-openapi
Upstream licenceMIT
Pinned at38170fdddbb6a1813eae6c6587ee17cf2987185b
API Commonshttps://apicommons.org/standards/models/ · https://github.com/api-commons/models

← All standards from practice