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

Responsible use

Most decisions can run fully automatically. Decisions about people in a few areas need a qualified person to review each one, a safety check flags requests that seek to harm people or help to self-harm (stricter blocking is set per customer), and military use needs a signed addendum. This page says what that means for your code.

on this page5 sections
  1. Automatic by default
  2. Decisions about people
  3. The safety check
  4. Military use
  5. Report misuse

The binding text is the policy

This page explains the Acceptable Use Policy and the Terms of Service for developers. Where the two differ, the legal pages apply.

Automatic by default#

Routing a ticket, gating an agent's tool call, checking an invoice against its order, moderating a post: set a threshold once, act on every answer above it, and take the safe path below it. Nothing has to wait for a person. The examples in these docs and in the playground are all of this kind.

Decisions about people#

A few areas are different. When DecisionNode helps make a consequential decision about a person in one of the categories below, a qualified person must review each decision before it takes effect. The answer can rank, flag and prepare the case; a person with the competence and the authority to change the outcome signs it off.

  • Hiring

    For example
    Screening, ranking or rejecting candidates, promotion and dismissal
  • Credit

    For example
    Approving, pricing or limiting a loan or a credit line
  • Housing

    For example
    Accepting or refusing a tenant, setting a deposit
  • Insurance

    For example
    Accepting a policy holder, pricing a premium, settling a claim
  • Education

    For example
    Admissions, grading that affects progression, discipline
  • Benefits

    For example
    Granting, reducing or stopping public or private benefits
  • Law enforcement

    For example
    Anything that leads to a stop, a search, a charge or a sentence
  • Health

    For example
    Diagnosis, treatment, triage and access to care
Categories that need a qualified person's review
CategoryFor example
HiringScreening, ranking or rejecting candidates, promotion and dismissal
CreditApproving, pricing or limiting a loan or a credit line
HousingAccepting or refusing a tenant, setting a deposit
InsuranceAccepting a policy holder, pricing a premium, settling a claim
EducationAdmissions, grading that affects progression, discipline
BenefitsGranting, reducing or stopping public or private benefits
Law enforcementAnything that leads to a stop, a search, a charge or a sentence
HealthDiagnosis, treatment, triage and access to care
  • Never on a protected trait. Do not ask DecisionNode to treat a person less favourably because of race, religion, sex, disability or another characteristic the policy lists. An attribute the decision genuinely depends on, such as income for a loan, is allowed where the law allows it.
  • No inferring sensitive traits such as health, religion or sexual orientation without the person's explicit consent or a legal basis.
  • Follow the law of your use case. Anti-discrimination, consumer protection, data protection and AI law (including the EU AI Act) apply to what you build; meeting them is your responsibility.

What review means in code

Hold the outcome until a qualified reviewer has signed it off, and apply it only then. Keep the request, the answer and the reviewer's decision together, so each decision can be explained later. See section 3 of the Acceptable Use Policy.

The safety check#

Every request to the hosted API is checked and, unless it is refused, answered. The check gives two calibrated probabilities: harm, that the request asks to choose, rank or target people to be hurt or killed, or to choose whom to harm by a protected attribute; and self_harm, that it seeks help to hurt oneself. Both come back on every response in the x-decisionnode-safety header, and in the body when you ask for them.

  • By default the check only flags: both probabilities come back in the header and the request is answered.
  • Stricter blocking is set per customer: flag or refuse either category at a threshold you choose. It can never be looser, and the self-harm check can never be switched off.
  • A refusal is 403 with {"detail": {"error_type": "refusal_error", "message": "...", "category": "self_harm"}} and no answers. It is not billed, and the same request is refused again.
  • As answers. With the request header x-decisionnode-refusals: per-question, a refused request on /v1/decide comes back as a 200 with a refusal answer for every question instead of the 403.
  • Detection is never refused. Asking whether a message shows a risk of self-harm, whether a post is a threat or whether a payment is fraud is answered as usual, and we encourage it.

Safety check has the header, the opt-in body, key policies and code; Errors has the refusal.

Military use#

Military use is not allowed under the standard terms. It is available only under a signed Defence Contract Addendum, which defence and security bodies of the member states of the North Atlantic Treaty Organization, the member states of the European Union, Australia, Japan, New Zealand and the Republic of Korea (and their contractors) may sign. Even under the addendum some uses stay forbidden in every case, including targeting people by a protected trait or targeting civilians, any weapon of mass destruction, and any decision to use force without a responsible person's authorisation.

Report misuse#

If you see DecisionNode used in a way these rules forbid, write to abuse@bynn.com. Security issues go to security@bynn.com.

previousRefer & earnnextData and privacy

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. Automatic by default
  2. Decisions about people
  3. The safety check
  4. Military use
  5. Report misuse