Use case · ticket routing

Send each ticket to the right queue

Pass the ticket and your queue names; get back the matching queue with a probability for every option. Tickets with a low probability can go to a human triager.

Get API key Read the quickstart

Example request

One call, five lines

Set DECISIONMODELS_API_KEY to a key from your dashboard. The request below uses the EU tier; send S1-Region: global for the Peer-to-Peer tier.

Request · POST /v1/systemone

curl https://api.decisionmodels.io/v1/systemone \
  -H "Authorization: Bearer $DECISIONMODELS_API_KEY" \
  -H "Content-Type: application/json" \
  -H "S1-Region: eu" \
  -d '{"model":"s1-fast","state":{"message":"I need to update my invoice address.","account_type":"business"},"questions":{"queue":{"type":"choice","instructions":"Choose the support queue that best fits the request.","criteria":{"billing":null,"technical":null,"account":null}}}}'

Example response

A typed answer with probabilities

Illustrative, not a measured model output. Always read the probability before your application acts on it.

Response · illustrative

{"id":"dec_example","model":"s1-fast","answers":{"queue":{"type":"choice","choice":"billing","confidence":0.87,"probabilities":{"billing":0.87,"technical":0.09,"account":0.04}}},"usage":{"input_tokens":351,"output_tokens":0,"decisions":1},"tier":"eu"}

Notes

Before you build on it

state can be plain text or a JSON object with the fields you have.
Add up to three questions per request with s1-pro (for example queue, urgency and language).
Use the EU tier when tickets contain personal data: inference stays in the EU.