API Reference

JEV SystemOne

JEV SystemOne

POST https://api.tu-zi.com/v1/systemone
Preview guide

Paste into an AI assistant to help with integration. Documentation and examples only; no real credentials.

Preview guide

JEV SystemOne

Updated · Reviewed

Endpoint and authentication

POST https://api.tu-zi.com/v1/systemone

Transport: json

Use an inference API key. Examples contain placeholders; read credentials from environment variables.

Authorization: Bearer YOUR_API_KEY
Content-Type: application/json

Minimal request example

{
  "model": "YOUR_MODEL",
  "state": "A support ticket",
  "questions": {
    "urgent": {
      "type": "choice",
      "criteria": {
        "yes": "Urgent",
        "no": "Not urgent"
      }
    }
  }
}

Before running

Replace https://api.tu-zi.com with this site origin (do not append /v1 twice), and YOUR_MODEL with the exact marketplace model ID. Install requests for Python; use Node.js 20+ and save JavaScript as .mjs. WebSocket samples list their own dependencies.

Create an inference key on the site and set API_KEY in the environment; replace YOUR_API_KEY in cURL. Prepare local input.png/input.wav files for upload examples.

Start with a minimal request, then read the result using the response fields below. For async APIs, a returned task ID requires polling; acceptance does not mean generation has finished.

Constraints

This page describes the base protocol. Use the selected model quick start for supported fields, enums, limits and asynchronous behavior. Replace YOUR_MODEL. Form initial values are not upstream defaults.

Body parameters

FieldTypeRequiredDescription / constraints
modelstringYesJEV model identifier, for example jev-1.13. Example: jev-1.13
statestring | objectYesBusiness state as text or a JSON object, such as ticket, order or alert context. Example: 请判断这条工单是否紧急
questionsobjectYesA nonempty JSON object defining questions: noul uses instructions; choice uses a criteria object; score uses a criteria array. Example: {"urgency":{"type":"choice","criteria":{"p0":"立即处理","p1":"尽快处理"},"instructions":"判断紧急等级"}}

Response fields

FieldTypeDescription / constraints
answersobjectNative answer object; Community may wrap it in data.answers.
usageobjectUsage when supplied by the provider.

Illustrative response; some endpoints show essential fields only. Optional fields may be absent.

{
  "answers": {
    "urgent": {
      "choice": "yes"
    }
  }
}

Errors and retries

Check HTTP status and protocol-specific errors; do not mix error formats across protocols. For 401/403 check credentials and permissions, for 429 back off, and for 5xx check gateway/upstream status. Error bodies may contain error/message/code depending on the protocol.

Use bounded exponential backoff for reads. Do not blindly retry task creation, generation, or key mutations, to avoid duplicate billing or execution.