Jev API idempotency keys
Stripe-style Idempotency-Key headers are not described on the System One page we used. Implement uniqueness in your database. Retries of 429/529 may repeat an evaluation; that is usually cheap. Repeating a transfer is not.
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
- Key the side effect (payout, ban, email) with your own idempotency store.
- You may re-POST the judgment if you accept token cost.
- Do not assume TypeSafe dedupes by a header we have not seen documented.
- Pair with async jobs so workers can safely restart.
Request / response shape
Official body has no documented idempotency field. Auth remains bearer. Body remains model, state, questions. Question ids are not sent to the model and are not idempotency keys. Official SDKs retry 429/529; that can produce two judgments for one user click.
Replay is for eval (same pin + body). Idempotency is for side effects. Do not retry 401 with the same key header — there is no official header, and 401 means fix the secret. Do not retry 422 until the body changes. Documented statuses only: 401, 422, 429, 529.
Pin jev-1.13.0 so two retries are at least the same weights. Aliases currently resolve there — confirm. Vendor claim: output free, input $0.042 / million — a repeated judgment is usually cheap; a repeated wire transfer is not. Schema-safe choice: approve_transfer is not proof you may execute twice. Inventing header names and calling them official is how integrations rot.
When not to expect TypeSafe dedupe
System One is a judgment API. If your worker restarts after a 200 you failed to persist, you must not fire the tool again. Store the decision id first.
Pitfalls
- Treating evaluation retries as proof the downstream tool was once-only.
- Inventing header names and calling them official.
- Retrying 401 with a fake idempotency header.
- Confusing replay with side-effect uniqueness.
See also
- API hub — judgment POST
- Errors and retries — when to back off
- Async jobs — restart-safe workers
- Replay pattern — eval, not payouts
FAQ
Is this a documented TypeSafe URL?
No.
Should I retry 401 with the same key header?
No. Fix the secret.
Replay vs idempotency?
Replay is for eval. Idempotency is for side effects.
Will TypeSafe return the cached answers if I resend?
Not in the public reference we used. You get another evaluation.
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/systemoneandGET /v1/modelsunless 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.