Comparisons· Last updated 2026-09-21

Jev versus asynchronous jobs: a practical comparison

An asynchronous job accepts work and finishes later. Jev still runs as a sync call inside the worker. The compare is whether the product should enqueue that call.

Unofficial operate page. docs.typesafe.ai. No keys.

Comparison scope

Bulk backfills, low-urgency triage, and “refresh labels overnight” belong on queues. Interactive gates may still be sync with a timeout.

Criteria that decide the architecture

Decision quality and control

Jobs let you honor 429 without failing the click. They also let labels go stale — show labeled_at in the UI.

Integration trade-offs

Enqueue {ticket_id, state_hash}. Worker calls pinned Jev. Write answers + response.model. Idempotent on state_hash.

TypeSafe’s public models page lists jev-1.13 at $0.042 per million input tokens with output tokens free — a vendor claim, not a jev.pro measurement. Confirm on the models page before you bid.

When each approach fits

Prefer Jev when

• The judgment can wait seconds to hours

Prefer Asynchronous jobs when

• The user must have the answer in this HTTP response and p95 allows it

Async is how you operate Jev at burst. Sync is how Jev is served.

What this page does not claim

• No invented job API on TypeSafe.

• Schema-safe output is not the same as factual correctness.

• No independent bake-off numbers live here.

FAQ

Does TypeSafe host my queue? No.

Poison messages? 422 → dead letter. Do not retry schema errors.

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.

Hub: Comparisons. Siblings: vs synchronous apis, vs batch processing, rest channel. Canonical: https://docs.typesafe.ai.