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 11

Discover models worth your attention

This is a Japanese DeBERTa V2 base model pre-trained on Japanese Wikipedia, the Japanese portion of CC-100, and the Japanese portion of OSCAR. The input text should be segmented into words by Juman++ in advance. Juman++ 2.0.0-rc3 was used for pre-training. Each word is tokenized into subwords by sentencepiece. Note that we filtered out documents annotated with "header", "footer", or "noisy" tags in OSCAR. Also note that Japanese Wikipedia was duplicated 10 times to make the total size of the corpus comparable to that of CC-100 and OSCAR. As a result, the total size of the training data is 171GB.

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

This is a Japanese DeBERTa V2 base model pre-trained on Japanese Wikipedia, the Japanese portion of CC-100, and the Japanese portion of OSCAR. This model is trained with character-level tokenization and whole word masking. There is no need to tokenize texts in advance, and you can give raw texts to the tokenizer. The texts are tokenized into character-level tokens by sentencepiece. - Japanese Wikipedia (as of 20221020, 3.2GB, 27M sentences, 1.3M documents) - Japanese portion of CC-100 (85GB, 619M sentences, 66M documents) - Japanese portion of OSCAR (54GB, 326M sentences, 25M documents)

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

This is a Japanese DeBERTa V2 large model pre-trained on Japanese Wikipedia, the Japanese portion of CC-100, and the Japanese portion of OSCAR. This model is trained with character-level tokenization and whole word masking. There is no need to tokenize texts in advance, and you can give raw texts to the tokenizer. The texts are tokenized into character-level tokens by sentencepiece. - Japanese Wikipedia (as of 20221020, 3.2GB, 27M sentences, 1.3M documents) - Japanese portion of CC-100 (85GB, 619M sentences, 66M documents) - Japanese portion of OSCAR (54GB, 326M sentences, 25M documents)

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

This is a Japanese DeBERTa V2 tiny model pre-trained on Japanese Wikipedia, the Japanese portion of CC-100, and the Japanese portion of OSCAR. The input text should be segmented into words by Juman++ in advance. Juman++ 2.0.0-rc3 was used for pre-training. Each word is tokenized into subwords by sentencepiece. Note that we filtered out documents annotated with "header", "footer", or "noisy" tags in OSCAR. Also note that Japanese Wikipedia was duplicated 10 times to make the total size of the corpus comparable to that of CC-100 and OSCAR. As a result, the total size of the training data is 171GB.

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

This is a Japanese DeBERTa V2 tiny model pre-trained on Japanese Wikipedia, the Japanese portion of CC-100, and the Japanese portion of OSCAR. This model is trained with character-level tokenization and whole word masking. There is no need to tokenize texts in advance, and you can give raw texts to the tokenizer. The texts are tokenized into character-level tokens by sentencepiece. - Japanese Wikipedia (as of 20221020, 3.2GB, 27M sentences, 1.3M documents) - Japanese portion of CC-100 (85GB, 619M sentences, 66M documents) - Japanese portion of OSCAR (54GB, 326M sentences, 25M documents)

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

The tokenizer of this model is based on huggingface/tokenizers Unigram byte-fallback model. The vocabulary entries were converted from `llm-jp-tokenizer v2.2 (100k)`. Please refer to README.md of `llm-jp/llm-ja-tokenizer` for details on the vocabulary construction procedure. Note that, unlike ku-nlp/deberta-v2-base-japanese, pre-segmentation by a morphological analyzer (e.g., Juman++) is no longer required for this model. We shuffled the corpora, which has 270B tokens in total, and trained the model for 2 epochs. Thus, the total number of tokens fed to the model was 540B.

Category pending
Input Not verified→ 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 ↗