JEV Demo

How to use Jev

Use Jev with a coding agent to build a decision workflow. Start with one clearly defined task and a small set of examples you can check yourself.

1. Set up your TypeSafe account

Open TypeSafe and follow its current access process. Sign in to the console when access is available. Access requirements and approval timing are controlled by TypeSafe.

Before integrating anything, choose the decision you want to automate: for example, assigning each incoming request to a department. Define the allowed answers and what should happen when none fits.

2. Install the TypeSafe skill

The skill gives your coding agent instructions for building a TypeSafe integration. Choose the installation method for your agent.

Codex and other supported agents

npx skills add typesafe-ai/skills --skill typesafe-ai

Select your agent when prompted.

Claude Code

claude plugin marketplace add typesafe-ai/skills
claude plugin install typesafe@typesafe-ai

These commands are published in the official skills repository. Installing the skill does not replace an API account or key.

3. Configure your API key

Create an API key in the TypeSafe console. Configure TYPESAFE_API_KEY in the local environment where your integration runs, or in your hosting provider’s server-side secret settings.

Keep the key out of public repositories and browser JavaScript. If you add a public interface later, route its API requests through your own backend. This guide does not need you to enter a key on JEV Demo.

4. Give your agent a specific task

Describe the input, the allowed decisions and how to handle uncertainty. Here is a starting prompt you can adapt:

Use the TypeSafe skill. Build a script that reads my sample support tickets and assigns each ticket to billing, technical support, sales or other. Return the decision and confidence, and flag uncertain cases for human review using a configurable threshold. Read the API key from TYPESAFE_API_KEY. Test only on my sample data and show the results alongside my expected labels. Do not send replies or change live tickets.

This is a proposed workflow, not a report of a completed test. Review the code and results before connecting it to live data.

Check the results before rollout

For an initial cost estimate, use the tokens calculator. Its savings percentages are assumptions you supply, not measured performance.