BAAI Models
Usage
40M
34.4K
4 of 4
- BAAI/bge-large-zh-v1.5
- bge-large-zh
- bge-large-en
- BAAI/bge-large-en-v1.5
- BAAI/bge-large-zh-v1.5
- bge-large-zh
- bge-large-en
- BAAI/bge-large-en-v1.5
Which models that traffic went to
- BAAI/bge-large-zh-v1.594.2%37.7M
- Bge Large Zh4.7%1.9M
- Bge Large En1.1%450K
- BAAI/bge-large-en-v1.5<0.1%7.1K
- BAAI/bge-large-zh-v1.592.6%31.9K
- Bge Large Zh7.0%2.4K
- Bge Large En0.3%100
- BAAI/bge-large-en-v1.50.1%30
All 4 BAAI Models
Open in model list| Modalities | ||
|---|---|---|
| BAAI/bge-large-en-v1.5 | Takes text, vision. Output modality not published. | $0.034$0.034/M |
| BAAI/bge-large-zh-v1.5 | Takes text, vision. Output modality not published. | $0.034$0.034/M |
| bge-large-en | Takes text, vision. Output modality not published. | $0.068$0.068/M |
| bge-large-zh | Takes text, vision. Output modality not published. | $0.068$0.068/M |
BAAI on AIHubMix
Which BAAI model should I start with?
BAAI/bge-large-en-v1.5 at $0.034/M input — the cheapest entry here that declares tool calling. Move up to bge-large-en when answer quality matters more than cost.
Why are there several entries for the same model?
Because each row is a route you can call, not a model release. Some IDs name an upstream (azure-, alicloud-, cc-), some are the open-weight repository form (BAAI/…), and some differ only in capitalisation, kept so older integrations keep working.
The catalog does not carry a field saying which of those a given row is, so this page does not sort them into buckets it would have to invent. Every row shows that route’s own price, context and speed — compare those directly, and open a model to see the upstreams that serve it.
Do I need a separate BAAI account?
No. One AIHubMix key covers every model on this page, and switching between them is a change to the model string — billing, rate limits, and logs stay in one place.
Start calling BAAI in one line
One key, one endpoint, 911 models across 42 model authors.

