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

Confidence

Probabilities are calibrated per question type, so a threshold means what it says on the data we measure. This page explains what calibrated means, how to check it on your own data, and how to choose where to draw the line.

on this page4 sections
  1. What calibrated means
  2. Where confidence lives in each type
  3. Choice confidence
  4. Score confidence
  5. Choosing a threshold
  6. Reading the numbers

What calibrated means#

Take every Truth answer the model gave near 0.9. If about nine in ten of those statements are actually true, the probabilities are calibrated. That is what makes a threshold meaningful: at 0.9 you accept about one wrong answer in ten among the ones that pass, and you can reason about that before you ship. Calibration is measured on our evaluation sets; it is an estimate, not a guarantee, so measure the error rate at your threshold on your own data before you rely on it.

Where confidence lives in each type#

  • Choice

    Field to gate on
    confidence
    Range and meaning
    0 when all options are equally likely, 1 when one option has all the probability
  • Score

    Field to gate on
    confidence, or a sum of probabilities
    Range and meaning
    How tightly the levels sit around the most likely one; tail sums answer "at least level n"
  • Truth

    Field to gate on
    truth
    Range and meaning
    The probability that the statement is true; distance from 0.50 is how sure it is
  • Number

    Field to gate on
    confidence, or a sum of probabilities
    Range and meaning
    The probability of number; add its neighbours for the chance the true value is within one
Confidence by question type
TypeField to gate onRange and meaning
Choiceconfidence0 when all options are equally likely, 1 when one option has all the probability
Scoreconfidence, or a sum of probabilitiesHow tightly the levels sit around the most likely one; tail sums answer "at least level n"
TruthtruthThe probability that the statement is true; distance from 0.50 is how sure it is
Numberconfidence, or a sum of probabilitiesThe probability of number; add its neighbours for the chance the true value is within one

Choice confidence#

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

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

Score confidence#

confidence = 1 − E[|i − m|] / D(K)

D(K) = floor(K · K / 4) / K

K
the number of levels
m
the most likely level, the lowest one on a tie
E[|i − m|]
the expected distance from m: sum(p_i · |i − m|)

Both are computed from the unrounded probabilities, then rounded to 2 decimals. A score's confidence is 1 when all the probability sits on one level, and probability next to the most likely level costs little. With two levels the two formulas agree. The Score page works one through.

Choosing a threshold#

  1. 1.Start at 0.7 for choice and number confidence and 0.8 for Truth gates.
  2. 2.Run a few hundred real inputs whose outcome you already know, such as resolved tickets or settled disputes.
  3. 3.For each threshold, measure two numbers: how many inputs pass, and how many of those are wrong.
  4. 4.Pick the threshold where the error rate is one your product can live with. Above it your code acts instantly; below it, it takes the safe action or re-checks with the full model.
  5. 5.Re-check after you change the questions or move to a new model version.

Thresholds belong to a question and a model

Changing the instructions, the options or the model version changes the distribution. Keep thresholds in config next to the question they belong to, and pin the model version in production.

Reading the numbers#

  • Two decimals. Every number in an answer is a JSON float rounded to 2 decimals, and whole values keep their decimal point: 1.0, 0.0, 3.0. Parse them as floats.
  • One exception: number. A number answer's number is a value of your grid, written as the grid writes it: 7 on a whole-number grid, 3.5 on a grid of 0.5. Its expected and confidence follow the float rule (7.0, not 7), and its probabilities are listed to 3 decimals. In a typed client, read number as a float; it always equals a grid value.
  • Clean fields. confidence, score and truth are always plain two-decimal values, and choice is always one of your option names.
  • probabilities can print long. After rounding, the largest entries of a choice's or a score's list are nudged by 0.01 toward a sum of 1, and a nudged entry can print as 0.8200000000000001. A few of those lists sum to 0.99 or 1.01. A number answer's list is to 3 decimals and is not nudged: its values sum to at most 1, and less over a wide grid. Thresholds and comparisons are unaffected; round before you display.
  • Read by key. Look answers up by question key and probabilities by option name or level, never by position: no order is part of the contract.
previousCollectionsnextDeterminism

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. What calibrated means
  2. Where confidence lives in each type
  3. Choice confidence
  4. Score confidence
  5. Choosing a threshold
  6. Reading the numbers