Skip to main content
These pages are the customer operations. Start with the quickstart if you have not sent a decision yet. Each operation below has its request and response schema, and you can try it with your own key.

Download OpenAPI spec

The spec the service serves at /openapi.json. It lists the same operations as this tab.

Move from Jev

Keep a Jev client. Change the address and the key. The path stays /v1/systemone.

The API at a glance

Most integrations call POST /v1/decide. The other customer routes are in the sidebar.

1. You send

A context and one or more decisions. Each decision has an id, a kind and the outcomes you define.

2. OneHot scores it

POST /v1/decide. One call, one context. The model returns a probability for every outcome.

3. You get

A probability for every outcome you allowed, and an action if you set a policy. model, version and fallback say which model answered.

POST /v1/decide

Start here. Get a probability for every outcome you defined. With a policy, the answer also says what to do, such as sending an unclear case to review.

POST /v1/decide/estimate

The maximum cost before you run it. No inference and no charge.

GET /v1/models

Base models and your fine-tuned models. A base or fine-tuned model says whether it is ready, and a model in a family has its switch (on_at). GET /v1/families lists your families.

POST /v1/systemone

The Jev request shape. Change the address and the key. See Move from Jev.
Read the response explains every field of an answer. Errors, retries and idempotency and limits have their own pages.