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. Patterns

Control loops

More than 10 decisions a second? Use a session. DecisionNode becomes the decision layer of a monitoring loop, a simulator or a drone's mission supervisor: it answers which mode or which action, and your own controller stays in charge of carrying it out.

on this page5 sections
  1. When to use a session
  2. A decision layer, never the controller
  3. The loop
  4. Designing frames
  5. What to build

When to use a session#

  • Now and then: a ticket, a payment, a tool call

    Use
    POST /v1/decide
    Why
    Each decision stands alone; one request, one answer
  • Many inputs at once

    Use
    Fan-out, or a batch job when it can wait
    Why
    Parallel requests within your rate limits, or a lower price when it can wait
  • More than 10 times a second, on one evolving input

    Use
    A session
    Why
    The context is sent once and stays loaded; each frame carries only what changed
Which call for which rate
You decideUseWhy
Now and then: a ticket, a payment, a tool callPOST /v1/decideEach decision stands alone; one request, one answer
Many inputs at onceFan-out, or a batch job when it can waitParallel requests within your rate limits, or a lower price when it can wait
More than 10 times a second, on one evolving inputA sessionThe context is sent once and stays loaded; each frame carries only what changed

The rule of thumb

More than 10 decisions a second about the same thing: open a session. Fewer, or about different things: call /v1/decide.

A decision layer, never the controller#

A vehicle runs in layers. The inner loop keeps it stable, many times a second, on its own controller. Above it sits a layer that decides what to do: continue or abort, which mode, which manoeuvre next. That is the layer a session serves. Its answers feed your controller, which stays in charge of the vehicle.

  • Mission and planning

    Decides
    The route, the task, the next job
    Runs on
    Your planner, with /v1/decide calls when it needs a judgment
  • Decision layer

    Decides
    Which mode now, continue or abort, the next action
    Runs on
    A DecisionNode session
  • Inner control loop

    Decides
    Attitude, speed, motors, brakes
    Runs on
    Your flight or motion controller, untouched
Where DecisionNode sits in a control stack
LayerDecidesRuns on
Mission and planningThe route, the task, the next jobYour planner, with /v1/decide calls when it needs a judgment
Decision layerWhich mode now, continue or abort, the next actionA DecisionNode session
Inner control loopAttitude, speed, motors, brakesYour flight or motion controller, untouched

Never the sole means of control

DecisionNode returns decision outputs. It is not designed, tested or certified as the only control of any vehicle, aircraft or machine whose failure could cause harm. Keep your controller, its own limits and an independent fallback in place, and follow the aviation and product-safety rules that apply to you. See the Terms.

The loop#

POST /v1/sessionsinstructions, state, questions, window 8

sent once, billed once

frames, each only what changedseq

  1. 7
  2. 8
  3. 9
  4. 10
  5. 11
  6. 12
  7. 13
  8. 14
  9. 15
  10. 16
  11. 17
  12. 18
  13. 19
window, last 8

replies, newest wins

    your controller

    mode

    continuereturn

    Takes the mode when the answer clears your threshold. It flies the vehicle, keeps its own limits and runs its own failsafe.

    A session opened once with instructions, state, questions and a window of 8 frames. Frames 15 to 19 stream in; each is answered on the fixed part plus the last 8 frames. Frames 17 and 18 arrive while 16 is being answered, so 18, the newest, is answered and the reply reports 17 as dropped. The reply to frame 19 says mode return with confidence 0.79 and abort 0.07, and your controller takes that mode.
    1. 1.Open a session once, with the mission brief as state and the questions every frame should answer. See Open a session.
    2. 2.On every tick, send only what changed as a frame: telemetry, a sensor reading, a camera frame. See Stream frames.
    3. 3.Hand each reply to your controller as a request, not a command: it applies the mode when the answer clears your threshold and the controller's own limits allow it.
    4. 4.When no fresh reply has arrived by your deadline, the controller keeps its current mode or runs its own failsafe. Your code decides that on its own, every time.
    5. 5.When the socket drops (1006), the server holding it goes away (1001), it fails on our side (1011), the session expires (4410) or goes idle (4408), open a new session with the same body and carry on. The controller keeps its mode meanwhile.
    6. 6.End the session when the mission ends. See End a session.

    Sessions has the complete supervisor in Python and TypeScript: one long-lived task reads your sensor feed, each session streams the newest reading, and a capped backoff reopens sessions after a drop.

    Designing frames#

    • Put the constant part in the session. The brief, the rules and the geofence go in state once as context; frames carry readings. Enforce the geofence and every flight limit in your flight controller, never through the model.
    • Keep frames small. A frame holds text or JSON of at most the session's max_frame_tokens (never more than 4,096 tokens; the open response gives the value), or one image. Name the fields (battery, wind_mps) so the model knows what each value is.
    • Choose the window for the decision. A mode change that depends on a trend needs a few recent frames; a reflex check on the current frame needs one. Send "reset": true when the situation changes completely, such as after landing.
    • Ask only what this tick needs. List questions on a frame to answer some of them; each frame is billed for the questions it asks.

    What to build#

    • Drones and vehicles, civilian: mission supervision for survey, inspection and delivery flights; return, hold and land decisions; mode selection.
    • Simulators and games: the next manoeuvre or action from a stream of state.
    • Industrial monitoring: machine state to action, alert or hold, from sensor frames.
    • Long-running agents: stream tool results and get a typed next step, without resending the whole context each time.

    Civilian use only, outside a Defence Contract Addendum

    Without a signed Defence Contract Addendum, sessions serve civilian control loops only: the Acceptable Use Policy forbids weapons, harmful payloads and targeting. Under an addendum, its own rules apply, and what its Section 4 forbids stays forbidden in every case.

    previousGuardrailsnextBatch jobs

    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. When to use a session
    2. A decision layer, never the controller
    3. The loop
    4. Designing frames
    5. What to build