Skip to content
DecisionNodeDecisionNdedocs
  • Guides
  • API reference
  • Examples
  • Playground

start here

  • QuickstartGet startedGet an API key, send one request with three questions, and branch your code on the typed answers. Plain HTTPS, nothing to install.
  • POST /v1/decideAPI referenceAnswer typed questions about a state, optional images and video frames. One request, one buffered JSON response, one answer per question.
  • QuestionsConceptsQuestions say what to decide. Each one has a type that fixes the shape of its answer: a choice from your options, a score on your scale, a…
  • ConfidenceConceptsProbabilities are calibrated per question type, so a threshold means what it says on the data we measure.
  • ImagesConceptsSend up to 16 images and text in the same request. The model reads printed and handwritten text, amounts, dates, objects and layout, and…
  • Batch jobsPatternsSend up to 10,000 requests in one file and collect the answers later, at a lower price than live calls.
  • Pricing and billingEvery workspace runs on a plan: Starter, Pro, Business or Dedicated.
↑↓ moveopen7 suggestions
Get API keyGet API key
DecisionNodeDecisionNde

Get started

  • Introduction
  • Quickstart
  • CLI
  • Playground
  • Console and keys
  • With coding agents
  • MCP server
  • Examples

Concepts

  • State
  • Questions
  • Choice
  • Score
  • Truth
  • Number
  • Points and boxes
  • Images
  • Video
  • Boosters
  • Collections
  • Confidence
  • Determinism
  • API keys

Knowledge

  • Overview
  • Documents
  • In a decision
  • Pricing and your data
  • When a rule does not appear

Models

  • DecisionNode
  • DecisionNode Flash
  • DecisionNode Edge
  • Limits
  • Versions
  • Dedicated capacity

Fine-tuning

  • Overview
  • Prepare your dataset
  • Upload and validation
  • Start a training run
  • Watch a run
  • The quality gate
  • Use your model
  • Limits and pricing

Patterns

  • Confidence-gated routing
  • Form router
  • Fan-out
  • Guardrails
  • Control loops
  • Batch jobs
  • Keys on devices
  • Bill your customers per device
  • Publishable keys

Integrations

  • Home Assistant
  • MQTT bridge
  • ROS 2

API reference

  • Overview
  • POST/v1/decide
  • POST/v1/systemone
  • GET/v1/models
  • POST/v1/uploads
  • /v1/keys
  • GET/v1/keys/{key_id}/usage
  • GET/v1/usage
  • POST/v1/credit
  • Errors
  • Safety check
  • Rate limits

Sessions API

  • Sessions overview
  • POSTOpen a session
  • WSStream frames
  • DELEnd a session

Collections API

  • Overview
  • POSTCreate a collection
  • GETList collections
  • GETRetrieve a collection
  • DELDelete a collection
  • POSTEnroll a face
  • GETList items
  • PATCHUpdate an item
  • DELDelete an item
  • POSTAdd a document
  • PUTReplace a document
  • GETRetrieve an item
  • GETList passages
  • DELDelete failed documents
  • POSTSearch a knowledge base

Batch API

  • The batch object
  • POSTCreate a batch
  • POSTAdd requests
  • POSTFinalize a batch
  • GETRetrieve a batch
  • GETGet batch results
  • POSTCancel a batch
  • GETList batches

Pricing and billing

  • Pricing and billing
  • Refer & earn

Policies

  • Responsible use
  • Data and privacy
  • Benchmarks
  • Pricing
  • Playground
Get API key
  • Guides
  • API reference
  • Examples
  • Playground

Get started

  • Introduction
  • Quickstart
  • CLI
  • Playground
  • Console and keys
  • With coding agents
  • MCP server
  • Examples

Concepts

  • State
  • Questions
  • Choice
  • Score
  • Truth
  • Number
  • Points and boxes
  • Images
  • Video
  • Boosters
  • Collections
  • Confidence
  • Determinism
  • API keys

Knowledge

  • Overview
  • Documents
  • In a decision
  • Pricing and your data
  • When a rule does not appear

Models

  • DecisionNode
  • DecisionNode Flash
  • DecisionNode Edge
  • Limits
  • Versions
  • Dedicated capacity

Fine-tuning

  • Overview
  • Prepare your dataset
  • Upload and validation
  • Start a training run
  • Watch a run
  • The quality gate
  • Use your model
  • Limits and pricing

Patterns

  • Confidence-gated routing
  • Form router
  • Fan-out
  • Guardrails
  • Control loops
  • Batch jobs
  • Keys on devices
  • Bill your customers per device
  • Publishable keys

Integrations

  • Home Assistant
  • MQTT bridge
  • ROS 2

API reference

  • Overview
  • POST/v1/decide
  • POST/v1/systemone
  • GET/v1/models
  • POST/v1/uploads
  • /v1/keys
  • GET/v1/keys/{key_id}/usage
  • GET/v1/usage
  • POST/v1/credit
  • Errors
  • Safety check
  • Rate limits

Sessions API

  • Sessions overview
  • POSTOpen a session
  • WSStream frames
  • DELEnd a session

Collections API

  • Overview
  • POSTCreate a collection
  • GETList collections
  • GETRetrieve a collection
  • DELDelete a collection
  • POSTEnroll a face
  • GETList items
  • PATCHUpdate an item
  • DELDelete an item
  • POSTAdd a document
  • PUTReplace a document
  • GETRetrieve an item
  • GETList passages
  • DELDelete failed documents
  • POSTSearch a knowledge base

Batch API

  • The batch object
  • POSTCreate a batch
  • POSTAdd requests
  • POSTFinalize a batch
  • GETRetrieve a batch
  • GETGet batch results
  • POSTCancel a batch
  • GETList batches

Pricing and billing

  • Pricing and billing
  • Refer & earn

Policies

  • Responsible use
  • Data and privacy
  1. docs
  2. /
  3. Concepts

Choice

A choice question picks exactly one option from the list you give and returns the probability of every option plus a confidence you can threshold.

on this page4 sections
  1. Request
  2. Response
  3. How confidence is computed
  4. Rounding and ties
Choice“Where should this go?”
  • account0.05
  • billing0.87
  • bug0.08

choice "billing"confidence 0.81

Request#

JSON
{
  "route": {
    "type": "choice",
    "instructions": "Where should this go?",
    "criteria": { "billing": "money", "bug": "broken", "account": "login" }
  }
}
type"choice"required
The question type.
criteriaobjectrequired
Option name to description, 1 to 255 options (two or more make a real choice). A name is any string, the empty string included, and comes back byte for byte. A description is a string, an object (by convention what, not_for and examples), an array, or null when the name says enough.
instructionsstring | object | array
What to decide. Optional: without it, the choice is answered from its options alone.

Response#

JSON
{
  "route": {
    "type": "choice",
    "choice": "billing",
    "confidence": 0.81,
    "probabilities": { "account": 0.05, "billing": 0.87, "bug": 0.08 }
  }
}
choicestring
The most likely option, taken from the unrounded probabilities. Always one of the keys you sent.
probabilitiesobject
One entry per option, zeros included, keyed by the option name exactly as sent. Listed alphabetically, but read them by key: the order is not part of the contract. They sum to 1, up to rounding.
confidencenumber
How sure the model is, from 0 to 1. See the formula below.

How confidence is computed#

confidence = (K · p_max − 1) / (K − 1)

K
the number of options you sent
p_max
the probability of the chosen option

Confidence is 0 when every option is equally likely and 1 when one option has all the probability. For the route above, K is 3 and p_max is 0.87, so confidence is (3 × 0.87 − 1) / 2 = 0.81. It is computed from the unrounded probabilities. Because it rescales by K, a confidence of 0.8 means the same thing on a 3-way and a 10-way choice.

Gate on confidence, not on p_max

A p_max of 0.6 is decisive among ten options and weak between two. Confidence corrects for that. See Confidence-gated routing.

Rounding and ties#

  • choice comes from the unrounded probabilities. Two options can both show 0.45 while one was slightly ahead before rounding, and on rare answers the named option is 0.01 below the largest value shown. Trust choice; do not re-derive it from the rounded list.
  • A tie goes to the option listed first in your request. Order the options so the one you prefer on a tie comes first.
  • The list sums to 1, up to rounding. Each probability is rounded to 2 decimals, then the largest are nudged by 0.01 toward a sum of 1. A nudged value can print as 0.8200000000000001, and a few lists still sum to 0.99 or 1.01. Compare numbers, never strings.
  • confidence is always a clean two-decimal value. It is computed before rounding, then rounded once.
previousQuestionsnextScore

DecisionNode is built and run by Bynn Intelligence, Inc.

  • Home
  • Playground
  • Examples
  • Console
  • Responsible use
  • Terms
  • Acceptable use
  • Privacy
  • Data processing
  • Defence addendum
  • Cookies
  • Affiliate program

on this page

  1. Request
  2. Response
  3. How confidence is computed
  4. Rounding and ties