Jev vs OpenAI Decisions API:
what changes for job matching?
Jev has a public API reference; OpenAI announced Decisions API in limited preview. Here is what the public information lets us compare.
Our launch choice: Jev
JevJob uses TypeSafe AI's documented Jev API. OpenAI's announcement describes a limited preview but does not publish a complete request-and-response contract.
| Consideration | Jev | OpenAI Decisions API |
|---|---|---|
| Availability | Public hosted API; provider guides are available. | Limited preview for selected API customers; broader access is planned in the coming days. |
| Input | Typed questions over a supplied text or JSON state. | Text or image context, with questions and possible answers defined by the developer. |
| Response | Typed choice, score, and yes/no probability (Noul) answers. | A selection from predefined answers; the public announcement does not specify the full response fields. |
| Integration method | Documented endpoint and server-side API key. | Endpoint, request schema and SDK support are not specified in the public preview post. |
| Pricing details | Usage-based provider API; review the current TypeSafe pricing before deployment. | No Decisions API price is stated in the public announcement; do not infer it from GPT-6 Luna's standard API price. |
| JevJob implementation | Selected for the launch matching workflow. | Not connected to JevJob; preview access does not change the current provider. |
Jev vs OpenAI Decisions API: accuracy
There is no controlled resume-to-job comparison of these two APIs here. Feature overlap alone does not prove equal accuracy or outputs.
Sources: OpenAI Developers announcement, OpenAI DevDay keynote, TypeSafe API quick start. Provider documentation and access can change; reviewed September 30, 2026.