API · Last updated

Jev API async jobs

Async jobs are your queue: enqueue a decision, a worker performs the official evaluation, then writes results. TypeSafe’s public reference is a synchronous POST.

This page is for builders who searched an extra “endpoint” name. 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. Persist the payload (state + questions + model pin) with a job id you generate.
  2. Worker calls POST /v1/systemone.
  3. Store answers, then mark the job complete.
  4. Expose status from your database — status pattern.
  5. Retry 429/529 on the worker, not by creating duplicate irreversible side effects.

Request / response shape

No job id comes back from TypeSafe. The evaluation response is the usual model / answers / usage object.

Pitfalls

See also

FAQ

Is there a documented /v1/jobs?

Not in the reference we used.

Timeouts?

Your worker deadline ≠ a TypeSafe job TTL we will invent.

Webhooks from TypeSafe when done?

Not documented. See webhook signatures.

What this page does not claim

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.

Sources