Skip to main content
POST
JEV-27B-VL

1. Overview

This document describes how to use the Decision Evaluation (Decide) capability through the AutoTrust JEV-27B-VL native protocol. Decision evaluation is not a chat, image, or video generation endpoint: a single request submits one piece of content to evaluate, state, and one question, question, and the endpoint synchronously returns the probability of each option for that question. The model supports mixing images into state, and is suited to scenarios that need a stable conclusion rather than free-form text, such as content moderation decisions, ticket routing, product categorization, and image-text consistency judgment. The call flow is a single request-response; there is no need to create a task or poll:
  1. Call the decision evaluation endpoint, specifying model, kind, state, and question in the request body (choice also requires options).
  2. Read the probability of each option from the response probabilities, or read choice directly.
  3. Read this request’s token usage from the response usage.
Only one question can be asked per request. To ask multiple questions about the same content, call the endpoint separately for each.

1.1 Endpoint

The full address in the examples in this document is https://api.novita.ai plus the endpoint path in the table above, where https://api.novita.ai is the API domain you use.

1.2 Authentication

All requests must carry an API Key and specify the JSON content type:

1.3 Response Structure

On success, the HTTP status code is 200 and the conclusion is returned directly:

2. Decision Evaluation

Official parameter documentation: autotrust/jev-27b-vl (inference.sh) · autotrust/JEV-27B-VL model card (the POST /v1/decide section)

2.1 Call Endpoint

Request fields: Passing images in state: write state as an array, with text as strings and images as {"image": "<URL or data URL>"}; images are inserted at the position they appear. Images support https:// public addresses or the data:image/...;base64,... form, up to 8 images. The larger the image, the more input tokens it consumes; a long edge of about 448 pixels is enough for most judgments.
Thinking mode: after thinking is enabled, the upstream calls the model for a round of reasoning in addition to the decision head, and fuses the two probability distributions with fixed weights. In this case usage.completion_tokens increases to the number of tokens used for thinking, num_model_requests is greater than 1, and the latency increases noticeably. The response contains an extra thinking object, including mode, threshold, budget, used, think_tokens, think_seconds, finished_within_budget, and, when return_reasoning=true, also the reasoning text. A single request body is at most 64 MB. The endpoint is a synchronous call; without thinking, upstream latency is usually under 0.2 seconds, and with thinking it grows with think_budget, so set a sufficiently long read timeout for your client.

2.2 Request Examples

A yes/no judgment with an image:

2.3 Response

On success, the conclusion is returned directly, with no need to query:
How to read the conclusion for the three question types: Use probabilities for threshold decisions; choice is only the highest-probability option and does not indicate confidence.

2.4 Billing

  • Only input tokens are billed, and the billed quantity is taken from the response usage.prompt_tokens, i.e. the number of input tokens actually counted by the upstream.
  • Image tokens are counted as input tokens.
  • Output tokens (usage.completion_tokens) are currently not billed, including tokens produced by enabling thinking mode.
  • Failed requests, or responses that do not contain usage, are not charged.
The exact unit price is subject to the pricing page of the service you use.

3. Common Errors and Notes

Endpoint errors use the following structure:
Other notes:
  • The model in the request body is fixed to autotrust/jev-27b-vl; the model in the response is the upstream echo autotrust/JEV-27B-VL. Both refer to the same model.
  • This endpoint and POST /v3/decisions (Jev 1.13) are two independent protocols: this endpoint asks one question per request and returns a probability array, while /v3/decisions asks multiple questions at once and returns an answers object. Do not mix their request bodies.
  • Validation of fields such as kind, options, and thinking is performed by the upstream, and the error information is returned with the response; correct your request based on that information.
  • Image URLs must be publicly accessible to the upstream and must not rely on an intranet, cookies, or a temporary login state; otherwise use an embedded data URL.
  • The model’s image judgment capability is zero-shot, and the official evaluation has not systematically measured its calibration on image scenarios; use image conclusions together with thresholds and business review.
  • Errors returned by the upstream are converted to the platform error structure shown in the table above; when troubleshooting, provide metadata.trace_id.

4. Python Example

The following example uses the standard requests library to demonstrate one complete call.
最終更新日 2026年10月19日