JEV / DEVELOPER DOCUMENTATION

Give your application a decision interface.

Connect to Jev through the System One SDK. Ask for a choice, a rubric score, or a probability, then decide how your application responds.

Make your first request Read the API reference

Probabilities inform application policy. They do not execute actions or guarantee correctness.

Request example · SDK 0.3.0

import { SystemOne, choice } from '@system-one-ai/sdk';

const client = new SystemOne({
  apiKey: process.env.SYSTEM_ONE_API_KEY!,
  baseURL: 'https://your-deployment.example.com/v1',
  maxRetries: 0,
});

const result = await client.evaluate({
  state: { message: 'I was charged twice.' },
  questions: {
    route: choice('Choose a team.', {
      billing: 'Payments and refunds',
      support: 'Technical help',
    }),
  },
}, {
  headers: { 'Idempotency-Key': crypto.randomUUID() },
});

Example input. No inference runs on this page.

From the first request to your own deployment

Connect the SDK

Install version 0.3.0, create a key, and set your deployment’s /v1 base URL.

Understand the answers

Keep choice distributions, weighted scores, and boolean probabilities in their native form.

Handle retries

Use one idempotency key per logical request and distinguish pending, failed, and replayed responses.

Plan credit usage

Estimate costs from question count and canonical UTF-8 bytes. Review prepaid credit packs.

Trace your data

Understand upstream processing, metadata retention, and the 24-hour answer replay cache.

Deploy on Workers

Configure Better Auth, D1, an upstream provider, and Stripe within TinyShip’s shared modules.