Land your first POST /v1/systemone

This note fills the missing stretch between /gateway and /jev: after you understand the decision layer, land the first live call. The flagship column stays on /jev. The product split stays on /gateway. This page only walks console key → POST /v1/systemone → read the response.

The path is one line:

1. Understand Jev: it does not write. Choice routes, Score bands, Noul gates.
2. Open the api.aijiau.com console, sign up, and create a site sk-....
3. POST https://api.aijiau.com/v1/systemone with model jev.

www /sign-in and /sign-up are the portal login, not the API console. Keys, Playground, and billing stay on the API host.

Do not use the chat door

Jev is TypeSafe’s System One decision model (public 15 September 2026). State plus typed questions go in. Choice / Score / Noul plus probabilities come out. It does not generate replies, code, or plans.

Chat getting started: OpenAI-compatible note. Price reading: One key, many models.

Create a site key

1. Sign up at https://api.aijiau.com/.
2. Create an sk-... in the console. Do not use a TypeSafe, OpenAI, or other upstream key.
3. Live catalog, balance, and chat model ids are whatever the console lists that day. This page does not paste a stale model table.

Public CS is [email protected].

Pasteable first call

Replace sk-your-aijiau-key with the key you just created. The shape matches the call panel on /jev and /jev/docs. The three questions evaluate in parallel and in isolation.

# Live Aijiau System One (0.2.1-aijia.99, SHA 8ff42e9)
# POST https://api.aijiau.com/v1/systemone  model: jev
# Protocol reference: POST https://api.typesafe.ai/v1/systemone
# Do not POST https://api.aijiau.com/v1/chat/completions with model jev — that returns 400
curl -sS -X POST https://api.aijiau.com/v1/systemone \
  -H "Authorization: Bearer sk-your-aijiau-key" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "jev",
    "state": "Customer: payment has failed for three days, order ORD-2024-1234, amount $299, needs handling now.",
    "questions": {
      "urgent": {
        "type": "noul",
        "instructions": "Is this issue urgent?"
      },
      "team": {
        "type": "choice",
        "instructions": "Which team should handle it?",
        "criteria": {
          "billing": "Payments, refunds, invoices",
          "technical": "Outages, API errors",
          "sales": "Pricing, new accounts"
        }
      },
      "frustration": {
        "type": "score",
        "instructions": "How frustrated is the customer?",
        "criteria": ["Calm", "Annoyed", "Very angry"]
      }
    }
  }'

Prefer a browser? Use the Playground. Do not treat api.aijiau.com/jev as a second homepage.

How to read the response

Machine docs record the answer shapes (TypeSafe API docs read 20 September 2026; Aijiau uses the same protocol). These are field shapes, not a live guarantee for one call, and not an SLA:

• Noul: { type: "noul", noul }. noul is 0 to 1. The current Noul response has no separate confidence. Your code owns the threshold.
• Choice: { type: "choice", choice, probabilities, confidence }. Low confidence is not a route.
• Score: { type: "score", score, legend, probabilities, confidence }. Adjacent scores have distance, so code can cut bands at thresholds.

TypeSafe documents a Choice cardinality cap of 255 and Score levels from 2 to 10. Official guidance is to split large questions, then compose in your own code.

Thresholds live in your policy, not in a prompt. Copy edits might pass at 0.65. Payments, deletes, and outbound sends may want 0.9 plus a second check. Those are starting points, not an aijiau-published accuracy.

Chinese and Traditional Chinese must be self-tested. TypeSafe says English is the main training language and has not published Simplified or Traditional numbers. The protocol and fixtures live at /jev/zh-eval. This page does not invent an accuracy percentage.

Common failures

The same-protocol alias POST https://api.aijiau.com/api/alpha/decisions still works. New code should hit the official POST /v1/systemone entry.

How to read prices

• aijiau customer price for Jev / System One on the live API host: ¥0.6 / 1M input, output free.
• TypeSafe vendor list price: $0.042 / 1M input, output free. Source: TypeSafe docs and product pages.
• Chat unit prices: whatever the console lists that day.

Do not mash these into a “we are N× faster” table. TypeSafe’s homepage 193.6× / 444.6× line is the high end of vendor workflow evals and must be read with their caveats; see /jev.

What this page does not claim

• No unpublished QPS, concurrency, uptime, or “fastest in China.”
• No Chinese / Traditional accuracy percentage. A gold-eval protocol is not a scoreboard.
• This page does not claim the api.aijiau.com router already uses Jev internally to pick models, retry, or block. The live host exposes model id jev on POST /v1/systemone.
• No tax quoting and no internal ops slang.
• Community clones (jevlike / OpenJev / NanoJev, jevai.dev) are not Jev.

Next

1. Still need the flagship column → /jev
2. Machine schema, errors, billing pointer → /jev/docs
3. Mixing Vercel boolean or LangChain Noul() → /jev/surfaces
4. Shipping Chinese tickets → /jev/zh-eval; build a gold set before you tune
5. Chat models only → OpenAI-compatible note

Humans stay on www. The first call stays on the console and this door: POST https://api.aijiau.com/v1/systemone.