AI NEWS · Model intelligenceExplore capabilities. Make informed choices. ↗Profiles indexed first · Details continuously enriched
THE AI MODEL DIRECTORY Start exploring models here

Find your ideal AI model.

From language to images, open weights to APIs. Understand capabilities and compare real costs.
Find the right engine for your next idea.

Popular searches
84,991 model profiles13202 providers / publishers45 capability categories465 with comparable prices · 30 benchmarked
TText generation▧Image generation▷Video generation⌘Code generation◖Speech synthesis♫Music generation⬡3D modeling▤Document analysis
DISCOVER & COMPARE

Explore AI models 2

Discover models worth your attention

Binary image classifier: `rain` vs `no_rain`, for a camera looking out a dock door. Fine-tuned from facebook/convnext-tiny-224 (Apache-2.0). Part of Kairos, a weather plugin for Boston Dynamics Spot fleets (Knight Hacks IX hackathon build). It feeds one input of a GO / HOLD rule. Python: `pipeline("image-classification", model="builtbyd3v/kairos-door-rain")`. Hold when p(rain) >= **0.4447** for q8, or >= **0.4728** for fp32 (each picked on the calibration split, one image per call). Both are in `eval_results.json` under `thresholds`. 95% CIs are Wilson score intervals. Threshold rule: the highest threshold that keeps calibration rain recall >= 95%, rounded down. Scored with onnxruntime CPU on the shipped ONNX files, one image per call (as in the browser).

Input Image→ Output Not verified
Price not verifiedCheck multimodal and channel pricing separately
View details ↗

Binary image classifier: `wet` (visible standing water or a wet surface) vs `dry`. Fine-tuned from facebook/convnext-tiny-224 (Apache-2.0). Built for SPOT Dispatch, a readiness board for Boston Dynamics Spot inspection routes. Spot's user guide says not to walk on wet or slippery surfaces, so the board can flag route photos that look wet for an operator to review. `onnx/model_quantized.onnx` (33.8 MB vs 111.4 MB fp32) loads with `{ dtype: "q8" }`. It is onnxruntime `quantize_dynamic`, uint8 weights, MatMul/Gemm layers only (convs stay fp32). Scored with onnxruntime on the same test split: q8 misses one more same-source wet image and changes 1 of 752 test predictions vs fp32 (kit images: same calls). Use fp32 when recall matters more than load time. Quantizing the convs too (28 MB) lost 2 same-source wet images, so it is not shipped.

Input Image→ Output Not verified
Price not verifiedCheck multimodal and channel pricing separately
View details ↗
COST EXPLORER

Great models. Clear costs.

Cost analysis

Adjust monthly token usage to compare estimated API costs.

1 M = 1 million tokens · USD
Compares base text-token rates within the same channel

Uses collected, comparable USD-per-million-token rates. Snapshots exclude cache discounts, tiers, extra reasoning output and taxes. Check current source prices.

MODEL HANDBOOK

Understand before you choose

Selection guide & FAQ
How should API prices be compared?+

Separate input, output and cache rates, then estimate the same workload. Image, audio and video rates may use items, duration or resolution rather than tokens.

Do open weights mean free commercial use?+

Not necessarily. Check each version’s license, commercial restrictions and policies. Self-hosting also incurs compute and maintenance costs.

Is the top-ranked model the best for me?+

Rankings depend on tasks, versions and methods. Compare accuracy, latency, reliability and costs on your own workload.

AI NEWS · From information to decisions

Follow trends. Find tools. Explore models.

Explore AI news ↗Discover AI tools ↗