openai_compatible_server.md 24.9 KB
Newer Older
1
2
3
4
---
title: OpenAI-Compatible Server
---
[](){ #openai-compatible-server }
5

6
vLLM provides an HTTP server that implements OpenAI's [Completions API](https://platform.openai.com/docs/api-reference/completions), [Chat API](https://platform.openai.com/docs/api-reference/chat), and more! This functionality lets you serve models and interact with them using an HTTP client.
7

8
In your terminal, you can [install](../getting_started/installation/README.md) vLLM, then start the server with the [`vllm serve`][serve-args] command. (You can also use our [Docker][deployment-docker] image.)
9

10
```bash
Reid's avatar
Reid committed
11
12
13
vllm serve NousResearch/Meta-Llama-3-8B-Instruct \
  --dtype auto \
  --api-key token-abc123
14
15
```

16
To call the server, in your preferred text editor, create a script that uses an HTTP client. Include any messages that you want to send to the model. Then run that script. Below is an example script using the [official OpenAI Python client](https://github.com/openai/openai-python).
17

18
??? Code
19

20
21
22
23
24
25
    ```python
    from openai import OpenAI
    client = OpenAI(
        base_url="http://localhost:8000/v1",
        api_key="token-abc123",
    )
26

27
28
29
30
31
32
33
34
35
    completion = client.chat.completions.create(
        model="NousResearch/Meta-Llama-3-8B-Instruct",
        messages=[
            {"role": "user", "content": "Hello!"}
        ]
    )

    print(completion.choices[0].message)
    ```
36

37
38
39
!!! tip
    vLLM supports some parameters that are not supported by OpenAI, `top_k` for example.
    You can pass these parameters to vLLM using the OpenAI client in the `extra_body` parameter of your requests, i.e. `extra_body={"top_k": 50}` for `top_k`.
40

41
!!! important
42
    By default, the server applies `generation_config.json` from the Hugging Face model repository if it exists. This means the default values of certain sampling parameters can be overridden by those recommended by the model creator.
43

44
    To disable this behavior, please pass `--generation-config vllm` when launching the server.
45

46
## Supported APIs
47

48
49
We currently support the following OpenAI APIs:

50
51
52
53
54
55
56
57
58
59
- [Completions API][completions-api] (`/v1/completions`)
    - Only applicable to [text generation models](../models/generative_models.md) (`--task generate`).
    - *Note: `suffix` parameter is not supported.*
- [Chat Completions API][chat-api] (`/v1/chat/completions`)
    - Only applicable to [text generation models](../models/generative_models.md) (`--task generate`) with a [chat template][chat-template].
    - *Note: `parallel_tool_calls` and `user` parameters are ignored.*
- [Embeddings API][embeddings-api] (`/v1/embeddings`)
    - Only applicable to [embedding models](../models/pooling_models.md) (`--task embed`).
- [Transcriptions API][transcriptions-api] (`/v1/audio/transcriptions`)
    - Only applicable to Automatic Speech Recognition (ASR) models (OpenAI Whisper) (`--task generate`).
60
61
- [Translation API][translations-api] (`/v1/audio/translations`)
    - Only applicable to Automatic Speech Recognition (ASR) models (OpenAI Whisper) (`--task generate`).
62

63
In addition, we have the following custom APIs:
64

65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
- [Tokenizer API][tokenizer-api] (`/tokenize`, `/detokenize`)
    - Applicable to any model with a tokenizer.
- [Pooling API][pooling-api] (`/pooling`)
    - Applicable to all [pooling models](../models/pooling_models.md).
- [Classification API][classification-api] (`/classify`)
    - Only applicable to [classification models](../models/pooling_models.md) (`--task classify`).
- [Score API][score-api] (`/score`)
    - Applicable to embedding models and [cross-encoder models](../models/pooling_models.md) (`--task score`).
- [Re-rank API][rerank-api] (`/rerank`, `/v1/rerank`, `/v2/rerank`)
    - Implements [Jina AI's v1 re-rank API](https://jina.ai/reranker/)
    - Also compatible with [Cohere's v1 & v2 re-rank APIs](https://docs.cohere.com/v2/reference/rerank)
    - Jina and Cohere's APIs are very similar; Jina's includes extra information in the rerank endpoint's response.
    - Only applicable to [cross-encoder models](../models/pooling_models.md) (`--task score`).

[](){ #chat-template }
80

81
## Chat Template
82

83
84
85
In order for the language model to support chat protocol, vLLM requires the model to include
a chat template in its tokenizer configuration. The chat template is a Jinja2 template that
specifies how are roles, messages, and other chat-specific tokens are encoded in the input.
86

87
An example chat template for `NousResearch/Meta-Llama-3-8B-Instruct` can be found [here](https://github.com/meta-llama/llama3?tab=readme-ov-file#instruction-tuned-models)
88

89
90
91
92
Some models do not provide a chat template even though they are instruction/chat fine-tuned. For those model,
you can manually specify their chat template in the `--chat-template` parameter with the file path to the chat
template, or the template in string form. Without a chat template, the server will not be able to process chat
and all chat requests will error.
93
94

```bash
95
vllm serve <model> --chat-template ./path-to-chat-template.jinja
96
97
```

98
vLLM community provides a set of chat templates for popular models. You can find them under the <gh-dir:examples> directory.
99

100
101
With the inclusion of multi-modal chat APIs, the OpenAI spec now accepts chat messages in a new format which specifies
both a `type` and a `text` field. An example is provided below:
102

103
104
```python
completion = client.chat.completions.create(
105
106
107
108
    model="NousResearch/Meta-Llama-3-8B-Instruct",
    messages=[
        {"role": "user", "content": [{"type": "text", "text": "Classify this sentiment: vLLM is wonderful!"}]}
    ]
109
)
110
111
```

112
Most chat templates for LLMs expect the `content` field to be a string, but there are some newer models like
113
114
115
116
`meta-llama/Llama-Guard-3-1B` that expect the content to be formatted according to the OpenAI schema in the
request. vLLM provides best-effort support to detect this automatically, which is logged as a string like
*"Detected the chat template content format to be..."*, and internally converts incoming requests to match
the detected format, which can be one of:
117

118
- `"string"`: A string.
119
    - Example: `"Hello world"`
120
- `"openai"`: A list of dictionaries, similar to OpenAI schema.
121
    - Example: `[{"type": "text", "text": "Hello world!"}]`
122

123
124
If the result is not what you expect, you can set the `--chat-template-content-format` CLI argument
to override which format to use.
125

126
## Extra Parameters
127

128
129
130
131
132
133
vLLM supports a set of parameters that are not part of the OpenAI API.
In order to use them, you can pass them as extra parameters in the OpenAI client.
Or directly merge them into the JSON payload if you are using HTTP call directly.

```python
completion = client.chat.completions.create(
134
135
136
137
138
139
140
    model="NousResearch/Meta-Llama-3-8B-Instruct",
    messages=[
        {"role": "user", "content": "Classify this sentiment: vLLM is wonderful!"}
    ],
    extra_body={
        "guided_choice": ["positive", "negative"]
    }
141
142
143
)
```

144
## Extra HTTP Headers
145

146
Only `X-Request-Id` HTTP request header is supported for now. It can be enabled
147
with `--enable-request-id-headers`.
148
149
150
151

> Note that enablement of the headers can impact performance significantly at high QPS
> rates. We recommend implementing HTTP headers at the router level (e.g. via Istio),
> rather than within the vLLM layer for this reason.
152
> See [this PR](https://github.com/vllm-project/vllm/pull/11529) for more details.
153

154
??? Code
155

156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
    ```python
    completion = client.chat.completions.create(
        model="NousResearch/Meta-Llama-3-8B-Instruct",
        messages=[
            {"role": "user", "content": "Classify this sentiment: vLLM is wonderful!"}
        ],
        extra_headers={
            "x-request-id": "sentiment-classification-00001",
        }
    )
    print(completion._request_id)

    completion = client.completions.create(
        model="NousResearch/Meta-Llama-3-8B-Instruct",
        prompt="A robot may not injure a human being",
        extra_headers={
            "x-request-id": "completion-test",
        }
    )
    print(completion._request_id)
    ```
177

178
179
## API Reference

180
[](){ #completions-api }
181

182
183
### Completions API

184
185
186
Our Completions API is compatible with [OpenAI's Completions API](https://platform.openai.com/docs/api-reference/completions);
you can use the [official OpenAI Python client](https://github.com/openai/openai-python) to interact with it.

187
Code example: <gh-file:examples/online_serving/openai_completion_client.py>
188
189

#### Extra parameters
190

191
The following [sampling parameters][sampling-params] are supported.
192

193
194
195
196
197
??? Code

    ```python
    --8<-- "vllm/entrypoints/openai/protocol.py:completion-sampling-params"
    ```
198
199
200

The following extra parameters are supported:

201
202
203
204
205
??? Code

    ```python
    --8<-- "vllm/entrypoints/openai/protocol.py:completion-extra-params"
    ```
206

207
[](){ #chat-api }
208

209
### Chat API
210

211
212
Our Chat API is compatible with [OpenAI's Chat Completions API](https://platform.openai.com/docs/api-reference/chat);
you can use the [official OpenAI Python client](https://github.com/openai/openai-python) to interact with it.
213

214
215
We support both [Vision](https://platform.openai.com/docs/guides/vision)- and
[Audio](https://platform.openai.com/docs/guides/audio?audio-generation-quickstart-example=audio-in)-related parameters;
216
see our [Multimodal Inputs][multimodal-inputs] guide for more information.
217
218
- *Note: `image_url.detail` parameter is not supported.*

219
Code example: <gh-file:examples/online_serving/openai_chat_completion_client.py>
220

221
#### Extra parameters
222

223
The following [sampling parameters][sampling-params] are supported.
224

225
226
227
228
229
??? Code

    ```python
    --8<-- "vllm/entrypoints/openai/protocol.py:chat-completion-sampling-params"
    ```
230
231
232

The following extra parameters are supported:

233
234
235
236
237
??? Code

    ```python
    --8<-- "vllm/entrypoints/openai/protocol.py:chat-completion-extra-params"
    ```
238

239
[](){ #embeddings-api }
240

241
242
### Embeddings API

243
244
Our Embeddings API is compatible with [OpenAI's Embeddings API](https://platform.openai.com/docs/api-reference/embeddings);
you can use the [official OpenAI Python client](https://github.com/openai/openai-python) to interact with it.
245

246
If the model has a [chat template][chat-template], you can replace `inputs` with a list of `messages` (same schema as [Chat API][chat-api])
247
248
which will be treated as a single prompt to the model.

249
250
251
252
253
254
255
Code example: <gh-file:examples/online_serving/openai_embedding_client.py>

#### Multi-modal inputs

You can pass multi-modal inputs to embedding models by defining a custom chat template for the server
and passing a list of `messages` in the request. Refer to the examples below for illustration.

256
=== "VLM2Vec"
257

258
    To serve the model:
259

260
261
    ```bash
    vllm serve TIGER-Lab/VLM2Vec-Full --task embed \
Reid's avatar
Reid committed
262
263
264
      --trust-remote-code \
      --max-model-len 4096 \
      --chat-template examples/template_vlm2vec.jinja
265
    ```
266

267
    !!! important
268
269
        Since VLM2Vec has the same model architecture as Phi-3.5-Vision, we have to explicitly pass `--task embed`
        to run this model in embedding mode instead of text generation mode.
270

271
272
        The custom chat template is completely different from the original one for this model,
        and can be found here: <gh-file:examples/template_vlm2vec.jinja>
273

274
    Since the request schema is not defined by OpenAI client, we post a request to the server using the lower-level `requests` library:
275

276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
    ??? Code

        ```python
        import requests

        image_url = "https://upload.wikimedia.org/wikipedia/commons/thumb/d/dd/Gfp-wisconsin-madison-the-nature-boardwalk.jpg/2560px-Gfp-wisconsin-madison-the-nature-boardwalk.jpg"

        response = requests.post(
            "http://localhost:8000/v1/embeddings",
            json={
                "model": "TIGER-Lab/VLM2Vec-Full",
                "messages": [{
                    "role": "user",
                    "content": [
                        {"type": "image_url", "image_url": {"url": image_url}},
                        {"type": "text", "text": "Represent the given image."},
                    ],
                }],
                "encoding_format": "float",
            },
        )
        response.raise_for_status()
        response_json = response.json()
        print("Embedding output:", response_json["data"][0]["embedding"])
        ```
301

302
=== "DSE-Qwen2-MRL"
303

304
    To serve the model:
305

306
307
    ```bash
    vllm serve MrLight/dse-qwen2-2b-mrl-v1 --task embed \
Reid's avatar
Reid committed
308
309
310
      --trust-remote-code \
      --max-model-len 8192 \
      --chat-template examples/template_dse_qwen2_vl.jinja
311
    ```
312

313
    !!! important
314
        Like with VLM2Vec, we have to explicitly pass `--task embed`.
315

316
317
        Additionally, `MrLight/dse-qwen2-2b-mrl-v1` requires an EOS token for embeddings, which is handled
        by a custom chat template: <gh-file:examples/template_dse_qwen2_vl.jinja>
318

319
    !!! important
320
321
        `MrLight/dse-qwen2-2b-mrl-v1` requires a placeholder image of the minimum image size for text query embeddings. See the full code
        example below for details.
322
323

Full example: <gh-file:examples/online_serving/openai_chat_embedding_client_for_multimodal.py>
324

325
#### Extra parameters
326

327
The following [pooling parameters][pooling-params] are supported.
328

329
330
331
```python
--8<-- "vllm/entrypoints/openai/protocol.py:embedding-pooling-params"
```
332

333
The following extra parameters are supported by default:
334

335
336
337
338
339
??? Code

    ```python
    --8<-- "vllm/entrypoints/openai/protocol.py:embedding-extra-params"
    ```
340

341
For chat-like input (i.e. if `messages` is passed), these extra parameters are supported instead:
342

343
344
345
346
347
??? Code

    ```python
    --8<-- "vllm/entrypoints/openai/protocol.py:chat-embedding-extra-params"
    ```
348

349
[](){ #transcriptions-api }
350
351
352
353
354
355

### Transcriptions API

Our Transcriptions API is compatible with [OpenAI's Transcriptions API](https://platform.openai.com/docs/api-reference/audio/createTranscription);
you can use the [official OpenAI Python client](https://github.com/openai/openai-python) to interact with it.

356
357
!!! note
    To use the Transcriptions API, please install with extra audio dependencies using `pip install vllm[audio]`.
358

359
Code example: <gh-file:examples/online_serving/openai_transcription_client.py>
360
361
<!-- TODO: api enforced limits + uploading audios -->

362
363
#### Extra Parameters

364
The following [sampling parameters][sampling-params] are supported.
365

366
367
368
369
370
??? Code

    ```python
    --8<-- "vllm/entrypoints/openai/protocol.py:transcription-sampling-params"
    ```
371
372
373

The following extra parameters are supported:

374
375
376
377
378
??? Code

    ```python
    --8<-- "vllm/entrypoints/openai/protocol.py:transcription-extra-params"
    ```
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
  
[](){ #translations-api }

### Translations API

Our Translation API is compatible with [OpenAI's Translations API](https://platform.openai.com/docs/api-reference/audio/createTranslation);
you can use the [official OpenAI Python client](https://github.com/openai/openai-python) to interact with it.
Whisper models can translate audio from one of the 55 non-English supported languages into English.
Please mind that the popular `openai/whisper-large-v3-turbo` model does not support translating.

!!! note
    To use the Translation API, please install with extra audio dependencies using `pip install vllm[audio]`.

Code example: <gh-file:examples/online_serving/openai_translation_client.py>

#### Extra Parameters

The following [sampling parameters][sampling-params] are supported.

```python
--8<-- "vllm/entrypoints/openai/protocol.py:translation-sampling-params"
```

The following extra parameters are supported:

```python
--8<-- "vllm/entrypoints/openai/protocol.py:translation-extra-params"
```
407

408
[](){ #tokenizer-api }
409

410
### Tokenizer API
411

412
Our Tokenizer API is a simple wrapper over [HuggingFace-style tokenizers](https://huggingface.co/docs/transformers/en/main_classes/tokenizer).
413
414
415
416
417
It consists of two endpoints:

- `/tokenize` corresponds to calling `tokenizer.encode()`.
- `/detokenize` corresponds to calling `tokenizer.decode()`.

418
[](){ #pooling-api }
419

420
421
422
423
### Pooling API

Our Pooling API encodes input prompts using a [pooling model](../models/pooling_models.md) and returns the corresponding hidden states.

424
The input format is the same as [Embeddings API][embeddings-api], but the output data can contain an arbitrary nested list, not just a 1-D list of floats.
425

426
Code example: <gh-file:examples/online_serving/openai_pooling_client.py>
427

428
[](){ #classification-api }
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453

### Classification API

Our Classification API directly supports Hugging Face sequence-classification models such as [ai21labs/Jamba-tiny-reward-dev](https://huggingface.co/ai21labs/Jamba-tiny-reward-dev) and [jason9693/Qwen2.5-1.5B-apeach](https://huggingface.co/jason9693/Qwen2.5-1.5B-apeach).

We automatically wrap any other transformer via `as_classification_model()`, which pools on the last token, attaches a `RowParallelLinear` head, and applies a softmax to produce per-class probabilities.

Code example: <gh-file:examples/online_serving/openai_classification_client.py>

#### Example Requests

You can classify multiple texts by passing an array of strings:

```bash
curl -v "http://127.0.0.1:8000/classify" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "jason9693/Qwen2.5-1.5B-apeach",
    "input": [
      "Loved the new café—coffee was great.",
      "This update broke everything. Frustrating."
    ]
  }'
```

454
??? Response
455

456
    ```bash
457
    {
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
      "id": "classify-7c87cac407b749a6935d8c7ce2a8fba2",
      "object": "list",
      "created": 1745383065,
      "model": "jason9693/Qwen2.5-1.5B-apeach",
      "data": [
        {
          "index": 0,
          "label": "Default",
          "probs": [
            0.565970778465271,
            0.4340292513370514
          ],
          "num_classes": 2
        },
        {
          "index": 1,
          "label": "Spoiled",
          "probs": [
            0.26448777318000793,
            0.7355121970176697
          ],
          "num_classes": 2
        }
481
      ],
482
483
484
485
486
487
      "usage": {
        "prompt_tokens": 20,
        "total_tokens": 20,
        "completion_tokens": 0,
        "prompt_tokens_details": null
      }
488
    }
489
    ```
490
491
492
493
494
495
496
497
498
499
500
501

You can also pass a string directly to the `input` field:

```bash
curl -v "http://127.0.0.1:8000/classify" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "jason9693/Qwen2.5-1.5B-apeach",
    "input": "Loved the new café—coffee was great."
  }'
```

502
??? Response
503

504
    ```bash
505
    {
506
507
508
509
510
511
512
513
514
515
516
517
518
519
      "id": "classify-9bf17f2847b046c7b2d5495f4b4f9682",
      "object": "list",
      "created": 1745383213,
      "model": "jason9693/Qwen2.5-1.5B-apeach",
      "data": [
        {
          "index": 0,
          "label": "Default",
          "probs": [
            0.565970778465271,
            0.4340292513370514
          ],
          "num_classes": 2
        }
520
      ],
521
522
523
524
525
526
      "usage": {
        "prompt_tokens": 10,
        "total_tokens": 10,
        "completion_tokens": 0,
        "prompt_tokens_details": null
      }
527
    }
528
    ```
529
530
531

#### Extra parameters

532
The following [pooling parameters][pooling-params] are supported.
533

534
535
536
```python
--8<-- "vllm/entrypoints/openai/protocol.py:classification-pooling-params"
```
537
538
539

The following extra parameters are supported:

540
541
542
```python
--8<-- "vllm/entrypoints/openai/protocol.py:classification-extra-params"
```
543

544
[](){ #score-api }
545

546
547
### Score API

548
Our Score API can apply a cross-encoder model or an embedding model to predict scores for sentence pairs. When using an embedding model the score corresponds to the cosine similarity between each embedding pair.
549
550
Usually, the score for a sentence pair refers to the similarity between two sentences, on a scale of 0 to 1.

551
You can find the documentation for cross encoder models at [sbert.net](https://www.sbert.net/docs/package_reference/cross_encoder/cross_encoder.html).
552

553
Code example: <gh-file:examples/online_serving/openai_cross_encoder_score.py>
554

555
556
557
558
#### Single inference

You can pass a string to both `text_1` and `text_2`, forming a single sentence pair.

559
```bash
560
561
562
563
564
565
566
567
568
569
curl -X 'POST' \
  'http://127.0.0.1:8000/score' \
  -H 'accept: application/json' \
  -H 'Content-Type: application/json' \
  -d '{
  "model": "BAAI/bge-reranker-v2-m3",
  "encoding_format": "float",
  "text_1": "What is the capital of France?",
  "text_2": "The capital of France is Paris."
}'
570
571
```

572
??? Response
573

574
    ```bash
575
    {
576
577
578
579
580
581
582
583
584
585
586
587
      "id": "score-request-id",
      "object": "list",
      "created": 693447,
      "model": "BAAI/bge-reranker-v2-m3",
      "data": [
        {
          "index": 0,
          "object": "score",
          "score": 1
        }
      ],
      "usage": {}
588
    }
589
    ```
590

591
#### Batch inference
592

593
594
595
You can pass a string to `text_1` and a list to `text_2`, forming multiple sentence pairs
where each pair is built from `text_1` and a string in `text_2`.
The total number of pairs is `len(text_2)`.
596

597
??? Request
598

599
600
601
602
603
604
605
606
607
608
609
610
611
612
    ```bash
    curl -X 'POST' \
      'http://127.0.0.1:8000/score' \
      -H 'accept: application/json' \
      -H 'Content-Type: application/json' \
      -d '{
      "model": "BAAI/bge-reranker-v2-m3",
      "text_1": "What is the capital of France?",
      "text_2": [
        "The capital of Brazil is Brasilia.",
        "The capital of France is Paris."
      ]
    }'
    ```
613

614
??? Response
615

616
    ```bash
617
    {
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
      "id": "score-request-id",
      "object": "list",
      "created": 693570,
      "model": "BAAI/bge-reranker-v2-m3",
      "data": [
        {
          "index": 0,
          "object": "score",
          "score": 0.001094818115234375
        },
        {
          "index": 1,
          "object": "score",
          "score": 1
        }
      ],
      "usage": {}
635
    }
636
    ```
637

638
639
640
641
You can pass a list to both `text_1` and `text_2`, forming multiple sentence pairs
where each pair is built from a string in `text_1` and the corresponding string in `text_2` (similar to `zip()`).
The total number of pairs is `len(text_2)`.

642
??? Request
643

644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
    ```bash
    curl -X 'POST' \
      'http://127.0.0.1:8000/score' \
      -H 'accept: application/json' \
      -H 'Content-Type: application/json' \
      -d '{
      "model": "BAAI/bge-reranker-v2-m3",
      "encoding_format": "float",
      "text_1": [
        "What is the capital of Brazil?",
        "What is the capital of France?"
      ],
      "text_2": [
        "The capital of Brazil is Brasilia.",
        "The capital of France is Paris."
      ]
    }'
    ```
662

663
??? Response
664

665
    ```bash
666
    {
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
      "id": "score-request-id",
      "object": "list",
      "created": 693447,
      "model": "BAAI/bge-reranker-v2-m3",
      "data": [
        {
          "index": 0,
          "object": "score",
          "score": 1
        },
        {
          "index": 1,
          "object": "score",
          "score": 1
        }
      ],
      "usage": {}
684
    }
685
    ```
686

687
#### Extra parameters
688

689
The following [pooling parameters][pooling-params] are supported.
690

691
692
693
```python
--8<-- "vllm/entrypoints/openai/protocol.py:score-pooling-params"
```
694

695
696
The following extra parameters are supported:

697
698
699
```python
--8<-- "vllm/entrypoints/openai/protocol.py:score-extra-params"
```
700

701
[](){ #rerank-api }
702
703
704

### Re-rank API

705
Our Re-rank API can apply an embedding model or a cross-encoder model to predict relevant scores between a single query, and
706
707
708
each of a list of documents. Usually, the score for a sentence pair refers to the similarity between two sentences, on
a scale of 0 to 1.

709
You can find the documentation for cross encoder models at [sbert.net](https://www.sbert.net/docs/package_reference/cross_encoder/cross_encoder.html).
710
711
712
713
714
715
716
717
718
719
720
721
722
723

The rerank endpoints support popular re-rank models such as `BAAI/bge-reranker-base` and other models supporting the
`score` task. Additionally, `/rerank`, `/v1/rerank`, and `/v2/rerank`
endpoints are compatible with both [Jina AI's re-rank API interface](https://jina.ai/reranker/) and
[Cohere's re-rank API interface](https://docs.cohere.com/v2/reference/rerank) to ensure compatibility with
popular open-source tools.

Code example: <gh-file:examples/online_serving/jinaai_rerank_client.py>

#### Example Request

Note that the `top_n` request parameter is optional and will default to the length of the `documents` field.
Result documents will be sorted by relevance, and the `index` property can be used to determine original order.

724
??? Request
725

726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
    ```bash
    curl -X 'POST' \
      'http://127.0.0.1:8000/v1/rerank' \
      -H 'accept: application/json' \
      -H 'Content-Type: application/json' \
      -d '{
      "model": "BAAI/bge-reranker-base",
      "query": "What is the capital of France?",
      "documents": [
        "The capital of Brazil is Brasilia.",
        "The capital of France is Paris.",
        "Horses and cows are both animals"
      ]
    }'
    ```
741

742
??? Response
743

744
    ```bash
745
    {
746
747
748
749
      "id": "rerank-fae51b2b664d4ed38f5969b612edff77",
      "model": "BAAI/bge-reranker-base",
      "usage": {
        "total_tokens": 56
750
      },
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
      "results": [
        {
          "index": 1,
          "document": {
            "text": "The capital of France is Paris."
          },
          "relevance_score": 0.99853515625
        },
        {
          "index": 0,
          "document": {
            "text": "The capital of Brazil is Brasilia."
          },
          "relevance_score": 0.0005860328674316406
        }
      ]
767
    }
768
    ```
769
770
771

#### Extra parameters

772
The following [pooling parameters][pooling-params] are supported.
773

774
775
776
```python
--8<-- "vllm/entrypoints/openai/protocol.py:rerank-pooling-params"
```
777
778
779

The following extra parameters are supported:

780
781
782
```python
--8<-- "vllm/entrypoints/openai/protocol.py:rerank-extra-params"
```