Data Sources

Data Sources

models aggregates data from multiple sources. This page describes where each type of data comes from and how it stays current.

Model data

• Source: models.dev, an open-source database of AI models maintained by SST
• Fetch strategy: Fetched from the models.dev API at TUI startup
• Coverage: 4,000+ models across 85+ providers
• Data includes: model names, IDs, providers, capabilities (reasoning, tools, files), pricing, context windows, modalities, release dates, knowledge cutoffs, open weights status

Benchmark data

• Source: Artificial Analysis
• Fetch strategy: Fetched fresh from a jsDelivr CDN endpoint on every launch (no local cache)
• Auto-updating: A GitHub Actions workflow fetches the latest data from the Artificial Analysis API every 30 minutes and commits changes to the repository. The CDN serves this data to all users.
• Coverage: ~400 model entries with quality indexes, individual benchmark scores, speed measurements, and pricing
• Data includes: Intelligence/Coding/Math/GPQA indexes, individual benchmark scores, tokens per second, latency, time to first token, input/output pricing, creator, region, reasoning capability, open/closed source

Agent data

• Source: Curated catalog in data/agents.json
• Coverage: 11 AI coding assistants
• Data includes: name, GitHub repo, categories (CLI/IDE), installation method, pricing model, supported providers, platform support, open source status, binary name, version detection commands, homepage and docs URLs
• Contributing: Adding a new agent to data/agents.json requires no Rust knowledge. See Contributing for details.

GitHub data

• Source: GitHub REST API
• Fetch strategy: Two modes depending on context:
  • TUI: 2 API calls per agent -- one for releases, one for repo metadata (stars, issues, license). Uses ETag conditional fetching with disk cache for fast startup.
  • CLI: 1 API call per agent -- releases only (no repo metadata needed). No caching.
• Cache: ~/.local/share/modelsdev/github-cache.json with configurable TTL (default: 1 hour). See Configuration#github-cache.
• Data includes: release versions, release dates, changelogs/release notes, star count, open issue count, license

Status data

• Source: Each provider's official status page
• Fetch strategy: Fetched on demand when the Status tab is active or when agents status shows the health column
• Platforms supported:
  • Statuspage (Atlassian) -- 13 providers
  • BetterStack -- 4 providers
  • Instatus -- 2 providers
  • incident.io -- 2 providers
  • Google (custom adapter) -- 1 provider
  • apistatuscheck.com -- fallback for all providers
• Data includes: overall health status, individual component/service statuses, active incidents with updates, scheduled and in-progress maintenance windows
• Fallback: If a provider's official status page is unreachable, apistatuscheck.com is used as a fallback source
• Coverage: 22 providers. See Status#tracked-providers for the full list.

Data flow summary

Data type	Fetched when	Cached	Update frequency
Models	TUI startup	No	Real-time from API
Benchmarks	Every launch	No	CDN updated every 30 min
Agents (catalog)	Embedded	N/A	Updated with releases
GitHub (releases, stars)	TUI startup / CLI command	Yes (ETag, 1h TTL)	On demand
Status	Tab active / CLI status	No	On demand