Developers

Modeldex already exposes a meaningful public API surface for models, providers, benchmarks, news, changelog data, and the MCP ecosystem. This page is the first step toward a fuller developer portal.

What you can use today

  • Build internal dashboards around models, providers, benchmarks, and changelog events
  • Power recommendation or comparison tools with structured catalog data
  • Track AI ecosystem movement without scraping HTML pages
  • Explore the MCP/tooling ecosystem with a machine-readable surface

Get started

Full usage analytics, formal API docs, webhooks, and SDKs are still in progress.

Core public endpoints

Early but already useful for building on top of the Modeldex catalog.

Base URL: https://modeldex.io/api
MethodPathDescription
GET/api/modelsList all models
GET/api/providersList providers
GET/api/benchmarksList benchmarks
GET/api/news?pageSize=5Latest news
GET/api/changelogRecent changelog entries
GET/api/mcp/statsMCP ecosystem stats

Authentication

Today the platform supports anonymous read access for many catalog endpoints, cookie auth for the web app, and bearer API keys for programmatic account-level calls.

Authorization: Bearer ***

Trust and data freshness

Modeldex mixes curated data, auto-synced ecosystem data, benchmark ingestion, changelog events, and community activity. That is useful, but it also means serious integrations should treat the platform as a living catalog and validate the exact surfaces they depend on.

  • Use provider and model detail pages to inspect freshness signals before relying on data operationally.
  • Expect some surfaces to evolve while the public API is still being productized.
  • Prefer explicit monitoring and selective rollout when wiring Modeldex data into downstream systems.

Repo quickstart

A written quickstart now exists inside the repo for the current public API shape, example endpoints, and the current maturity level of the developer surface.

docs/runbooks/public-api-quickstart.md