Dante / The decision API

Decisions,
ready for
your code.

Turn context into booleans, choices, and scores.
Define the possible answers. Get the probabilities.

A REQUEST. THREE ANSWERS.Explore a decision
Decision explorerRECORDED MODEL RESPONSE
01 YOUR CONTEXT

“I was charged twice for my order. Please refund the extra payment.”

Which team should handle this?
billingshippingtechnical
02 THE DECISION
billing
Option probability99.97%
needs_action 99.3% yesurgency 1.48 / 2
2.6B parametersBoolean / Choice / ScoreHosted decision API
THE SHAPE OF AN ANSWER

An answer your software
can act on.

Use Dante wherever your application needs to make a judgment. You define the question and the available answers.

Distributions from the recorded support request below.
THE PLAYGROUND

Try Dante on your
next decision.

Edit an example or add a request from your workflow. Run the model and inspect the probability behind each answer.

dante / decision-lab
Connecting
01 / INPUTstate: string
Edit the example or use your own.
3 defined questions View instructions
choiceroute

Which team should handle this request?

billing · shipping · technical

booleanneeds_action

Does this customer need help with a payment issue?

scoreurgency

Rate the urgency of this request.

Low: general information · Medium: a problem needing follow-up · High: immediate action needed

Demo limit: 2,048 tokens per pass

02 / OUTPUTRECORDED SAMPLE
routechoice
billing
billing
100.0%
shipping
0.0%
technical
0.0%
needs_actionboolean
99.3% yes
yes
99.3%
no
0.7%
urgencyscore
1.48 / 2
low
4.9%
medium
42.6%
high
52.5%
5,500 msMODEL TIME
131INPUT TOKENS
0GENERATED TOKENS

Recorded model response. Run the request for a fresh result.

Inspect response JSON
{
  "model": "dante-latest",
  "answers": {
    "route": {
      "type": "choice",
      "probabilities": {
        "billing": 0.9997,
        "shipping": 0.0002,
        "technical": 0.0001
      },
      "choice": "billing",
      "confidence": 0.9996
    },
    "needs_action": {
      "type": "noul",
      "noul": 0.9928
    },
    "urgency": {
      "type": "score",
      "probabilities": {
        "0": 0.0489,
        "1": 0.4261,
        "2": 0.525
      },
      "score": 1.4761,
      "legend": {
        "0": "Low: general information",
        "1": "Medium: a problem needing follow-up",
        "2": "High: immediate action needed"
      },
      "confidence": 0.7381
    }
  },
  "usage": {
    "input_tokens": 131,
    "output_tokens": 194
  },
  "latency_ms": 5499.7
}
MADE FOR YOUR STACK

Ask several questions in one request.

Send context and questions to the Dante API. Get structured answers your application can use.

A hosted API for your application
Text or JSON context, typed results
Multiple questions over shared context
Try the request
POST /v1/systemone
{
  "model": "dante-latest",
  "state": "I was charged twice for my order. Please refund the extra payment.",
  "questions": {
    "route": {
      "type": "choice",
      "instructions": "Which team should handle this request?",
      "criteria": {
        "billing": "Charges, payments, and refunds",
        "shipping": "Delivery and tracking",
        "technical": "Broken features or login problems"
      }
    },
    "needs_action": {
      "type": "noul",
      "instructions": "Does this customer need help with a payment issue?"
    },
    "urgency": {
      "type": "score",
      "instructions": "Rate the urgency of this request.",
      "criteria": [
        "Low: general information",
        "Medium: a problem needing follow-up",
        "High: immediate action needed"
      ]
    }
  }
}
Dante API · JSON request and response
YOUR WORKFLOW, YOUR RULES

Set the rules for your next action.

Use the returned probabilities to route a request or send it for review. Set the threshold in your own code and evaluate it against your use case.

Move the slider to see how a threshold changes the next action.

YOUR APPLICATION LOGICinteractive example
billing99.97%

Option probability from the recorded request.

0%100%
probability >= 0.900 ? route() : review()
Send to billing
A FEW DETAILS

Before you
make the call.

The model, the API,
and the answers.