Quick Start: Get Your First Jev Request Running in 30 Minutes
💡 Goal: Get your TypeSafe API Key within 30 minutes and run your first Jev request locally—one ticket text, and in a single call get three structured answers: "which group to route it to, how frustrated the customer is, and whether it's urgent." This is the first stop of the entire Jev tutorial.
🎯 Stage Goals
- Obtain a TypeSafe API Key and store it in the environment variable
TYPESAFE_API_KEY - Run your first Jev request locally: one ticket text, and in a single call get three answers—a classification, a score, and a yes/no
- When errors occur, be able to locate the problem by status code: 401 check the Key, 429 is rate limiting, 400 check the request format
⏳ Estimated Time
- Just want to get the first request running: study the first 3 lessons (1.1–1.3), totaling about 23 minutes; 30 minutes is more than enough
- Complete the entire stage (including alternative installation methods and troubleshooting): 5 lessons totaling about 37 minutes, roughly 26–48 minutes with buffer time
🚀 Before You Start
- A computer with internet access and a terminal (the official quick start commands are written in Bash for macOS / Linux / Windows WSL)
- Python 3.10 or higher (the main route uses the Python SDK; the Node.js 22+ route is covered in lesson 1.3b)
- Network access to
console.typesafe.ai(to get the Key) andapi.typesafe.ai(to send requests) - A cup of water ☕—getting your first run working really takes less than 30 minutes
📚 Lessons in This Stage
| Lesson | Content | Duration |
|---|---|---|
| 1.1 What Is Jev | The System One decision model, how it differs from an LLM, and the three question types: Choice / Score / Noul; entirely using the official Playground, no coding | 8 minutes |
| 1.2 Registration and API Key | Get the Key from the TypeSafe console, store it in the environment variable TYPESAFE_API_KEY, and where to check rate limits | 5 minutes |
| 1.3 Installation and First Request | Install typesafe-sdk with venv + pip and run the official ticket three-question example | 10 minutes |
| ↳ 1.3b Alternative Installation Methods | uv, npm (JavaScript / TypeScript SDK), and calling the API directly with curl | 8 minutes |
| 1.4 Getting Started Troubleshooting | Status code reference for 401 / 429 / 400 and others, SDK automatic retries, and common pitfalls | 6 minutes |
🎒 What You'll Gain
- An API Key and a working typesafe-sdk environment, reused directly in all subsequent stages
- Your first complete experience of "state + questions → typed answers"
- A feel for the three question types—Choice / Score / Noul—and the intuition for choosing among them
- A status code reference table, so you can self-check before asking for help when stuck