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 84991

Discover models worth your attention

tinytowns

dave8172

基础档案已收录,详细介绍后续补充。可先查看厂商、分类与来源。

Basic profile indexed · More details to follow

Input Text→ Output Text
Price not verifiedCheck multimodal and channel pricing separately
View details ↗

MeaningBERT

davebulaval

MeaningBERT is an automatic and trainable metric for assessing meaning preservation between sentences. MeaningBERT was proposed in our article MeaningBERT: assessing meaning preservation between sentences. Its goal is to assess meaning preservation between two sentences that correlate highly with human judgments and sanity checks. For more details, refer to our publicly available article. > This public version of our model uses the best model trained (where in our article, we present the performance results > of an average of 10 models) for a more extended period (500 epochs instead of 250). We have observed later that the > model can further reduce dev loss and increase performance. Also, we have changed the data augmentation technique used > in the article for a more robust one, that also includes the commutative property of the meaning function. Namely, Meaning(Sent_a, Sent_b) = Meaning(Sent_b, Sent_a). The repository root holds the **v1** model described in the article, unchanged, so anything already using `from_pretrained("davebulaval/MeaningBERT")` keeps returning exactly the scores it returned before.

Input Text→ Output Text
Price not verifiedCheck multimodal and channel pricing separately
View details ↗

scglm-v2-46m

davemaxuellkr

基础档案已收录,详细介绍后续补充。可先查看厂商、分类与来源。

Basic profile indexed · More details to follow

Input Text→ Output Text
Price not verifiedCheck multimodal and channel pricing separately
View details ↗

NudtyFix

Daverrrr75

基础档案已收录,详细介绍后续补充。可先查看厂商、分类与来源。

Basic profile indexed · More details to follow

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

INT8 `W8A16` quantization of Blackfrost-AI/Qwen3.8-27B-ABLITERATED-BF16, which is itself an abliterated derivative of `Qwen/Qwen3.8-27B`. > **On this hardware int8 is SLOWER than BF16** — roughly half the decode rate — > and MTP speculative decoding does not work. Both are measured below. Use these > only if you need the smaller memory footprint. Weights 8-bit, **group size 128**, symmetric. Activations are **not** quantized (`pack-quantized`), so this is weight-only int8.

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

A **W4A16 (AWQ)** quantization of `Blackfrost-AI/Qwen3.8-Flash-Next-DERISKED-BF16`, an abliterated ("derisked") variant of Qwen's Qwen3.8-Flash-Next. Multimodal (image-text-to-text), MTP speculative-decode head and PLE n-gram table preserved. Built to run the 80B-class Flash-Next MoE on 2× AMD MI210 (gfx90a) at long context. - **Format:** `compressed-tensors`, **W4A16** — 4-bit weights, group size **128**, symmetric, no zero-point (loads on vLLM's `TritonW4A16` + `fused_moe_kernel_gptq_awq` fast paths). - **Method:** **AWQ** (activation-aware). Smoothing is restricted to the mathematically-exact `up_proj → down_proj` pairs. The standard `norm → q/k/v` and `norm → gate/up` smoothings are deliberately **excluded**: this architecture uses hyper-connections with a data-dependent (sigmoid) gate, so folding a smoothing scale into the norm would change the gate non-linearly and corrupt the weights. - **Quantized:** routed experts (gate/up/down) and full-attention `q/k/v/o`. - **Kept in bf16** (matching the reference recipe): the GDN linear-attention layers (recurrent state — error compounds along the sequence), the shared expert, the QSA indexer, the router gates, hyper-connections, norms, `embed_tokens`, `lm_head`, the **MTP** speculative-decode head, and the **PLE** n-gram embedding table.

Input Text · Image→ Output Text
Price not verifiedCheck multimodal and channel pricing separately
View details ↗

EgoX

DAVIAN-Robotics

基础档案已收录,详细介绍后续补充。可先查看厂商、分类与来源。

Basic profile indexed · More details to follow

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

pi05_droid_jointpos

DAVIAN-Robotics

基础档案已收录,详细介绍后续补充。可先查看厂商、分类与来源。

Basic profile indexed · More details to follow

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

my-fusion-v1

David-kim

基础档案已收录,详细介绍后续补充。可先查看厂商、分类与来源。

Basic profile indexed · More details to follow

Input Text→ Output Text
Price not verifiedCheck multimodal and channel pricing separately
View details ↗

Two versions of Command-R-01 35B using TWO new DARK HORROR Neo Imatrix datasets bring an INTENSE horror upgrade to Command-R 01 35B. I created the HORROR datasets using Grand Horror 16B using 90+ different horror prompts for generation. This process created an incredibility intense, visceral and vivid horror stories in an ultra compact form - perfect for an Imatrix NEO class dataset. The dataset is focused exclusively on visceral, vivid horror based on phycological horror. (rather than "gore" or "body part horror"). There is some swearing the dataset, so this might appear in generation.

Input Text→ Output Text
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 ↗