BAAI Models

5 modelsGeneral models from $0.03/M input

Usage

Last 30 days · 2026-07-13 to 2026-08-11

Tokens

29.6B

Requests

955K

Models in use

5 of 5

Tokens per day

0631M1.3B07-1307-2007-2708-0308-102026-07-13 — 797,651,420 tokens2026-07-14 — 919,672,205 tokens2026-07-15 — 818,052,935 tokens2026-07-16 — 991,839,375 tokens2026-07-17 — 852,884,895 tokens2026-07-18 — 846,849,050 tokens2026-07-19 — 742,632,595 tokens2026-07-20 — 970,558,310 tokens2026-07-21 — 1,122,893,340 tokens2026-07-22 — 1,053,474,730 tokens2026-07-23 — 1,022,854,415 tokens2026-07-24 — 990,963,140 tokens2026-07-25 — 961,907,190 tokens2026-07-26 — 778,287,450 tokens2026-07-27 — 1,021,572,610 tokens2026-07-28 — 969,886,190 tokens2026-07-29 — 1,016,377,840 tokens2026-07-30 — 926,528,575 tokens2026-07-31 — 1,200,155,290 tokens2026-08-01 — 1,002,474,025 tokens2026-08-02 — 818,452,610 tokens2026-08-03 — 901,382,615 tokens2026-08-04 — 1,119,161,055 tokens2026-08-05 — 1,098,696,445 tokens2026-08-06 — 1,077,298,695 tokens2026-08-07 — 1,038,032,735 tokens2026-08-08 — 1,111,690,375 tokens2026-08-09 — 1,063,360,220 tokens2026-08-10 — 1,261,013,440 tokens2026-08-11 — 1,117,089,765 tokens

Which models that traffic went to

  1. BAAI/bge-reranker-v2-m399.0%29.3B
  2. BAAI/bge-large-en-v1.50.9%275M
  3. bge-large-zh<0.1%7.5M
  4. BAAI/bge-large-zh-v1.5<0.1%3.9M
  5. bge-large-en<0.1%644K

Share of 29.6B tokens.

The two views disagree on purpose: a model can take a large share of the calls and a small share of the tokens — many short requests — or the reverse. Which one matters depends on whether your cost is driven by call volume or by prompt length. Measured on AIHubMix over the last 30 days, counting the 5 model IDs listed on this page; traffic routed through upstream-specific IDs that are not in the public catalog is not included.

All 5 BAAI Models

Open in model list
BAAI models on AIHubMix with input and output modalities, context length, maximum output, price per million tokens including cache read and cache write rates, and measured throughput and latency.
Modalities
BAAI/bge-large-en-v1.5Takes text, vision. Output modality not published.$0.03$0.03/M
BAAI/bge-large-zh-v1.5Takes text, vision. Output modality not published.$0.03$0.03/M
BAAI/bge-reranker-v2-m3Takes text, vision. Output modality not published.$0.03$0.03/M
bge-large-enTakes text, vision. Output modality not published.$0.07$0.07/M
bge-large-zhTakes text, vision. Output modality not published.$0.07$0.07/M

Prices are USD per million tokens; cache read and cache write are the rates for prompt-cache hits and for writing a prompt into the cache. Throughput and latency are measured on AIHubMix — the same figures the model detail page shows — not vendor claims. A dash means the catalog does not publish that field for that model, which is not the same as the model not supporting it.

BAAI on AIHubMix

Which BAAI model should I start with?

BAAI/bge-large-en-v1.5 at $0.03/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, 844 models across 35 providers.