API · Last updated 2026-09-21

Jev API route endpoint

Routing is a documented pattern: classify, then send the ticket to deterministic code, an LLM, or a human. There is no documented /v1/route that performs the handoff.

This page is for builders who searched an extra “endpoint” name while wiring Jev / System One. jev.pro is an independent unofficial field guide — not affiliated with TypeSafe AI. We do not sell or issue keys. Confirm first-party routes on docs.typesafe.ai/api.

The public API reference documents one evaluation route — POST https://api.typesafe.ai/v1/systemone — plus GET /v1/models. This title is not a separate first-party URL in that reference. Treat the capability as something you implement around the official call.

Steps

1. Choice intent (+ optional Score complexity) in one POST.
2. Apply confidence floors before you obey the winner (confidence-gated routing).
3. Your router calls the handler. Jev does not enqueue Slack.
4. Keep other / abstain as first-class exits.

Map onto the official POST

Same evaluation body: model, state, questions. Choice is unordered, max 255. Score is 2–10 ordered levels. Noul is P(yes) without confidence — do not copy Noul τ onto Choice confidence. Question ids are not sent to the model. Your service’s /route is yours.

Pin jev-1.13.0 once floors exist. Aliases jev-latest and jev-preview currently resolve to it — confirm. Documented HTTP errors: 401, 422, 429, 529. Official SDKs retry 429/529. Vendor-claimed 1200 RPM and $0.042 / million input (output free) apply to the judgment, not to your Slack enqueue.

Schema-safe ≠ the ticket belongs on that team. Executing rank 2 as a silent second guess hides the hold you should have taken. Model routing (which LLM to call) and ticket routing (which queue) are both your code after a Choice.

When not to invent /v1/route

If you need TypeSafe to push work to a bus, you are asking for a webhook they have not documented on System One. Keep the handoff in your worker.

Pitfalls

• Executing rank 2 as a silent second guess.
• Copying Noul τ onto Choice confidence.
• Calling /v1/route.
• Letting an option name look like a permission check.

See also

• API hub — evaluation POST
• Intent routing — classify then dispatch
• Confidence-gated routing — floors
• Classify pattern — Choice, not /v1/classify

FAQ

Is /v1/route documented?

No.

Model routing vs ticket routing?

Both are your code after a Choice — model routing.

Official pattern page?

TypeSafe: intent routing / confidence-gated routing.

Does Jev enqueue Slack?

No. Your router does.

What this page does not claim

• Official TypeSafe status, logos, or support.
• That jev.pro sells, issues, or proxies API keys.
• Extra first-party HTTP routes beyond POST /v1/systemone and GET /v1/models unless the API reference lists them.
• Invented latency SLOs, search volume, or unofficial prices. List price and rate limits are vendor claims — confirm on models.
• That a schema-constrained answer is automatically factually correct.

Disclaimer

This is an independent unofficial site and is not affiliated with TypeSafe AI; official documentation is available at https://docs.typesafe.ai. Never treat jev.pro as TypeSafe official documentation. We do not sell, issue, or proxy API keys.