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
41,859 model profiles6815 providers / publishers45 capability categories464 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 1433

Discover models worth your attention

**Note:** Check out my new, updated models: German_Semantic_V3 and V3b! This is a sentence-transformers model: It maps sentences & paragraphs to a 1024 dimensional dense vector space and can be used for tasks like clustering or semantic search. Special thanks to deepset for providing the model gBERT-large and also to Philip May for the Translation of the dataset and chats about the topic.

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

This is a sentence-transformers model finetuned with wandb-ai from sentence-transformers/all-MiniLM-L6-v2. It maps sentences & paragraphs to a 384-dimensional dense vector space and can be used for semantic textual similarity, semantic search, paraphrase mining, text classification, clustering, and more. For this case, it uses for column standardization.

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

FRIDA

ai-forever

FRIDA is a full-scale finetuned general text embedding model inspired by denoising architecture based on T5. The model is based on the encoder part of FRED-T5 model and continues research of text embedding models (ruMTEB, ru-en-RoSBERTa). It has been pre-trained on a Russian-English dataset and fine-tuned for improved performance on the target task. For more model details please refer to our article (RU). The model's results are presented on the MTEB and rusBEIR leaderboards. The model can be used as is with prefixes. It is recommended to use CLS pooling. The choice of prefix and pooling depends on the task.

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

ru-en-RoSBERTa

ai-forever

The ru-en-RoSBERTa is a general text embedding model for Russian. The model is based on ruRoBERTa and fine-tuned with ~4M pairs of supervised, synthetic and unsupervised data in Russian and English. Tokenizer supports some English tokens from RoBERTa tokenizer. The model can be used as is with prefixes. It is recommended to use CLS pooling. The choice of prefix and pooling depends on the task. We use the following basic rules to choose a prefix: - `"search_query: "` and `"search_document: "` prefixes are for answer or relevant paragraph retrieval - `"classification: "` prefix is for symmetric paraphrasing related tasks (STS, NLI, Bitext Mining) - `"clustering: "` prefix is for any tasks that rely on thematic features (topic classification, title-body retrieval)

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

PatentSBERTa

AI-Growth-Lab

This is a sentence-transformers model: It maps sentences & paragraphs to a 768 dimensional dense vector space and can be used for tasks like clustering or semantic search. Without sentence-transformers, you can use the model like this: First, you pass your input through the transformer model, then you have to apply the right pooling-operation on-top of the contextualized word embeddings. For an automated evaluation of this model, see the *Sentence Embeddings Benchmark*: https://seb.sbert.net

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

Для получения более подробной информации о технических деталях, пожалуйста, обратитесь к нашей статье. Для достижения более точных результатов при работе с эмбеддингами, особенно в задачах поиска и извлечения информации (retrieval), рекомендуется добавлять инструкцию на естественном языке перед текстовым запросом (query). Это помогает модели лучше понять контекст и цель запроса, что положительно сказывается на качестве результатов. Важно отметить, что инструкцию нужно добавлять только перед запросом, а не перед документом. Для **симметричных задач**, таких как классификация (classification) или семантическое сравнение текстов (semantic text similarity), инструкцию необходимо добавлять перед каждым запросом. Это связано с тем, что такие задачи требуют одинакового контекста для всех входных данных, чтобы модель могла корректно сравнивать или классифицировать их.

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

Следующая итерация серии Giga-Embeddings. Модель текстовых эмбеддингов на основе архитектуры Qwen3, адаптированная под **двунаправленное (encoder-style) внимание** и обученная с контрастивной функцией потерь (InfoNCE). Модель строит плотные эмбеддинги предложений/абзацев для задач поиска (retrieval), семантического сравнения, классификации и кластеризации, показывая высокое качество на русском и английском языках. Модель обучалась с **mean pooling + L2-нормализацией**. Использование CLS/last-token пулинга даст неверные результаты. Если вы используете `transformers` напрямую, необходимо самостоятельно усреднить (mean-pool) по не-паддинговым токенам и затем применить L2-нормализацию (см. пример ниже). В примерах для `sentence-transformers` и vLLM это делается автоматически. Сравнивайте эмбеддинги через косинусную близость (скалярное произведение нормированных векторов). Модель обучалась в **инструктивном стиле**: для retrieval и других асимметричных задач необходимо добавлять инструкцию к **запросу** (query), а документы кодируются как есть, без инструкции. Формат:

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