Skip to main content
These are the same five steps as the onboarding page in the dashboard, which can also run them for you. You need an API key. To get one, sign up in the dashboard:
  1. Name your organization and choose a plan.
  2. Add a card on the secure payment page. Billing on your plan starts then: see signing up.
  3. Create your API key: read-write, scoped to default/*, and shown once. You can create more on the dashboard’s Keys page.
If you leave before adding a card, sign-up picks up there when you come back. New organizations are limited each day. If sign-ups are full when you sign up, you go on the waitlist and we email you when there’s room. default/quickstart is a free place to try things. It holds up to 10,000 documents and 100 MB (a write past that is refused with too_large), and its judging pauses for the rest of the billing period at a small usage limit (pricing). For real data, write to a namespace of your own.
1

Install the SDK

2

Create a client

The namespace does not exist yet. It is created by its first write or judgment.
3

Define a judgment

Start from the ticket triage starter: a ready-made judgment that asks whether a ticket is urgent. Tell it where your documents keep the subject, the first message and the customer’s plan:
This creates a bool judgment named urgent, with its question, criteria, context recipe and an urgent threshold at 0.8. definition in the response shows all of it. Add dry_run to see it and its cost first without creating anything, or write your own definition instead; see judgments.on_change computes the answer whenever a document changes, so every document has a current answer to filter or sort on. Jev current runs whichever Jev model the provider serves now; each answer records the epoch of model behaviour that produced it in engine_version, such as current+2026-09-24.1, and a new epoch starts only when we detect the model’s behaviour change. See the engines page.
4

Write three documents

The write is durable once it returns. wait_for also waits until the answers exist, which usually takes a few seconds. Without it, the write returns in a fraction of a second and the answers follow.
5

Query by the answer

Each answer carries its probability p, the urgent threshold as a boolean, its freshness, and the revision, judgment version and engine version it was computed with.

​
Next