AI Models 1.1.0 includes 1,806 model records and 47 provider entry points. For enterprise teams that frequently switch models, this kind of unified catalog is more useful than digging through another set of vendor documentation.
What this is
AI Models is a developer-focused catalog that brings model names, pricing, context length, protocols, regional plans, and API addresses—the endpoints developers use to call models—into one place. Version 1.1.0 also adds a timeline of flagship model releases and a “model PK” feature for comparing costs across providers.
The new version supports filtering by provider, price, context length, open-source status, domestic Chinese models, and flagship status. Tags such as “free” and “domestic” follow explicit labeling rules, while unverified listings are classified as “unknown” rather than judged solely by their names. The API catalog covers four protocols: OpenAI Chat Completions, OpenAI Responses, Anthropic Messages, and Google Generative AI.
Industry view
We believe its primary value is addressing information friction in enterprise AI procurement. What companies usually need is not “which model is strongest,” but which provider is cheaper for the same task, which plan fits their existing API keys, and whether the integration endpoint is correct. By providing a common basis for comparison and links to vendor sources, the catalog offers a practical starting point for model selection.
The risks are equally clear. Model pricing, exchange rates, and plan terms change, and the catalog may not synchronize in real time. A model resold through different platforms may also differ in capability, reliability, and data-handling conditions. Its “SOTA” label is manually verified; it is not a continuously updated benchmark ranking. The “free” tag requires both cached-input and image pricing to be zero, meaning real-world promotional allowances are not necessarily the same as long-term free access. The catalog can therefore narrow the field, but final purchasing decisions should still rely on the provider’s latest contract and tests using real requests.
Impact on regular people
For enterprise IT: Teams can complete initial model and provider screening faster, reducing the need to repeatedly search documentation and copy endpoint addresses before testing real business samples for cost and quality.
For individual professionals: Even users without coding expertise can use the catalog to understand differences between models. However, enterprise purchasing decisions should still be jointly reviewed by technical, legal, and procurement teams, especially to verify data compliance and service terms.
For the consumer market: A unified pricing catalog will increase price transparency across models. However, end-user application subscriptions will not necessarily fall in step with wholesale prices, since compute costs, platform margins, and operating expenses sit between the two.