← Back to Scout

HOW SCOUT WORKS

Sources & methodology.

How Privaj Scout collects model metadata, labels evidence, estimates memory, and handles missing information.

Sources and coverage

Scout uses the documented Hugging Face Hub API to retrieve limited public metadata from selected organizations. The current import requests up to 200 recent repositories per tracked organization. Reaching this limit can leave older models out.

Download formats with recognized suffixes may be grouped with their exact base model; different parameter sizes and fine-tunes stay separate. Cloud catalogs and pricing imports are currently paused.

Qwen200 listings · import limit reached · Retrieved
ornith-ai26 listings · Retrieved
deepseek-ai104 listings · Retrieved
meta-llama70 listings · Retrieved
mistralai75 listings · Retrieved
google200 listings · import limit reached · Retrieved
microsoft200 listings · import limit reached · Retrieved
black-forest-labs35 listings · Retrieved
stabilityai117 listings · Retrieved
Wan-AI27 listings · Retrieved
Lightricks57 listings · Retrieved
nvidia200 listings · import limit reached · Retrieved
zai-org154 listings · Retrieved
MiniMaxAI21 listings · Retrieved
moonshotai19 listings · Retrieved
openai39 listings · Retrieved

How we use source data

We retain model identifiers, maker names, capability and license labels, reported parameter and context sizes, source timestamps, and links. Scout writes its own short summaries. We do not copy full model cards, download model weights, bypass access gates, or republish benchmark tables.

Ollama is not connected. OpenRouter imports are paused, and its previously imported records and fields have been removed pending clarification of reuse permissions. A public API or model license alone does not establish permission to reuse every associated piece of content.

Source requests are cached and rate limited. Requests stop on rate-limit responses and resume after the retry window. Hub API documentation ↗ · Rate limits ↗ · Hugging Face terms ↗

Facts, estimates, and unknowns

Capabilities and plain-language summaries are derived from source metadata, not an independent performance evaluation. Vision means visual input; image generation means image output. 3D generation alone does not establish CAD capabilities.

Parameter counts use reported metadata when available, otherwise a recognizable nominal size in the model’s name. A 4-bit memory baseline uses total parameters × 4 ÷ 8, in decimal GB. Extra runtime and cache memory are not included, and compatible quantization is not guaranteed.

Hugging Face’s memory estimation reference ↗

“Downloadable” does not mean unrestricted open source. The permissive-license filter recognizes MIT, Apache, BSD, and ISC labels. Read the exact model license before use.

Dates, freshness, and availability

Listing dates are repository creation or catalog addition dates, not confirmed launch dates. Last checked records when Scout retrieved that information. Removed listings remain in the archive; verify availability at the source.

The explorer checks visible-page updates every five minutes, with longer pauses when the source requests backoff. The configured Lenovo service also checks sources in the background, saves updates on disk, and keeps seven daily local backups. A local preview without persistent storage uses its bundled snapshot after a restart.

How comparisons work

There is no overall intelligence score, paid ordering, or automatic winner. The default ordering is recently listed first; other explicit sorts use names or reported context sizes. Missing measurements do not become zero.

Comparison graphs highlight specific measurements, such as theoretical weight memory, when enough comparable data is available. Smaller memory does not establish better intelligence or guaranteed hardware fit.

No third-party benchmark tables or scores are currently imported. Adding them requires checking reuse permissions, attribution, and comparable test settings. Comparisons across different model categories do not assign shared performance scores.

Corrections and limitations

A source-backed catalog still reflects which sources we track and the limits of their metadata. We cannot promise complete coverage or zero bias. Missing values remain visible, and previous data may be stale.

To challenge a detail, send a correction with the original source. A public correction history is not yet available.