兔子API 兔子API
中

model

Jev-1.13

Direct answerCall /v1/systemone from the marketplace with state and questions, then read native answers or Community data.answers for triage, routing, and risk decisions.

Updated · Reviewed

Model characteristics

Jev-1.13 is a typed decision model. It maps facts to executable, structured answers instead of writing essays or holding a long conversation. It fits ticket triage, risk assessment, routing, policy pre-screening, and human-review gates. Multiple questions can be answered in one request, keeping urgency, action, and escalation signals together.

Request shape

Send model, state, and a non-empty questions object to POST /v1/systemone. choice takes an object in criteria; score takes a low-to-high ordered array; noul describes a yes/no judgment in instructions. The marketplace tester includes a multi-question choice, score, and noul example that can be adapted to real business facts.

Response handling

JevAI Community returns a code, message, and data envelope, with answers under data.answers. AIHubMix and OpenRouter return top-level answers and may include usage. The gateway preserves the native structure. Answer fields vary by question type and can include choice, score, probabilities, legend, and confidence. Parse by question name and answer type; do not treat probabilities as facts or depend on field order.

Gateway limits and billing

The current adapter is synchronous and non-streaming, rejects stream, and limits the body to 32 KiB. Upstream usage is preferred when present. Community may omit usage; when it does, the gateway estimates input tokens from the JSON request. Prices come from marketplace configuration.

Safe use

Put only the minimum business facts needed for a decision in state. Never include Agent Keys, gateway keys, passwords, tokens, or unnecessary personal data. Keep human approval, authorization checks, timeouts, and model-failure fallbacks for high-impact actions.

Use cases

  • Ticket urgency and action decisions
  • Risk scoring and human escalation

API protocols

  • /v1/systemone

FAQ

Is Jev-1.13 compatible with Chat Completions?

The gateway integration exposes native /v1/systemone only. It does not map JEV requests to messages or recommend parsing choices[0].message.content.

How should state and questions be filled?

state can be a string or JSON object containing the minimum facts needed for the decision. questions must be non-empty, with type, instructions, and type-appropriate criteria.

Can score criteria be an object?

No. score uses an ordered low-to-high array. choice uses an option-to-description object, while noul normally needs no criteria.

How is billing estimated without usage?

Community may omit usage. The gateway estimates input tokens from the request JSON and applies the marketplace model price, marked as estimated billing.

  • JevAI structured decision modelsJEV turns business facts into choice, score, and noul signals. On this gateway, use the /v1/systemone endpoint for the Community integration.
  • API endpoint and capability matrixConfirm the exact model and enabled endpoint in the marketplace first, then select a protocol here. A registered route only means the gateway recognizes it, not that every model or channel supports it.
  • AI API quickstart: from API key to first requestAn AI API call needs a matching base URL, API key, model ID, and endpoint; start with minimal curl, then add error handling, cost controls, and key security.

Official sources

  1. JevAI API docs Official
  2. AIHubMix JEV docs Official