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

State

The state is the thing you are deciding about. It can be any text, a JSON object or a JSON array. It is read once per request and shared by every question.

on this page5 sections
  1. What to send
  2. How the model sees it
  3. Read once, shared by every question
  4. Writing a good state
  5. Size

What to send#

Send the input exactly as your system has it. A support message can go as a string; a ticket with its metadata reads better as JSON, because field names tell the model what each value is.

{
  "state": "Customer: I was charged twice and nobody has replied for 3 days."
}

state is optional. A question can stand alone when its instructions carry everything, for example a Truth check on a sentence you put in the instructions. Leaving state out, sending "" and sending null all mean the same: no state.

How the model sees it#

  • A string

    The model reads
    The string exactly as sent, never re-serialised, also when it holds a JSON document (compact, spaced or indented)
  • An object or an array

    The model reads
    Compact JSON with your key order kept. Nested objects, arrays, numbers, booleans, null and empty values are all fine
  • Nothing, "" or null

    The model reads
    No state: the questions are answered from their own text
  • A bare number or boolean, such as 42 or true

    The model reads
    Nothing: the request is a 422. Wrap it, as "42" or { "count": 42 }
What each form of state becomes
You sendThe model reads
A stringThe string exactly as sent, never re-serialised, also when it holds a JSON document (compact, spaced or indented)
An object or an arrayCompact JSON with your key order kept. Nested objects, arrays, numbers, booleans, null and empty values are all fine
Nothing, "" or nullNo state: the questions are answered from their own text
A bare number or boolean, such as 42 or trueNothing: the request is a 422. Wrap it, as "42" or { "count": 42 }

Key order is kept, so the same object sent with its keys in another order is a different state to the model and can get a slightly different answer. Build states the same way every time.

Read once, shared by every question#

The model encodes the state and any images once, then answers every question in the request from that single read. Ten questions about one ticket cost the state's tokens once plus each question's own tokens, so ask everything you need in one request rather than one request per question.

One input, one request

If you find yourself sending the same state twice with different questions, merge the questions. It is cheaper and every answer comes from the same read. See Fan-out.

Writing a good state#

  • Label what matters. { "plan": "team" } says more than the word team floating in a paragraph.
  • Leave out what does not. Large blocks of unrelated text make every decision harder. Trim logs, signatures and quoted history that do not bear on the decision.
  • Keep it stable. Send fields in the same order and format every time. The model is deterministic, so a stable state gives stable answers.
  • Do not put instructions in the state. Put them in each question's instructions, so the state stays pure data and one state serves many questions.

Size#

A request holds up to 64k tokens (65,536), counting the state, the images and every question. usage.input_tokens in the response tells you what a request used. See Limits.

previousExamplesnextQuestions

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 to send
  2. How the model sees it
  3. Read once, shared by every question
  4. Writing a good state
  5. Size