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

Dedicated capacity

Capacity on our own GPUs reserved for your traffic, with limits set for your deployment, or the models on your own hardware for qualifying deployments. The same API, the same answers.

on this page6 sections
  1. When to use it
  2. What stays the same
  3. What changes
  4. On your premises
  5. Health check
  6. How to ask for it

When to use it#

  • Your steady traffic is above what the default rate limits of a few keys cover, and you want headroom that is yours alone.
  • You need capacity reserved for your traffic alone, designed to keep other customers' bursts off your hot path.
  • Your cameras or lines need DecisionNode or DecisionNode Flash next to them: on premises or at the edge, for a qualifying deployment. For a model you download and run yourself, see DecisionNode Edge.
  • You are a defence or security body of an eligible state and need the models inside your own network.

What stays the same#

A dedicated deployment answers the same API: POST /v1/decide, sessions, batch jobs and GET /v1/models, with the same request and response shapes, the same errors and the same models. The same request to the same pinned version returns the same answer as on the shared API, so tests, thresholds and replays carry over unchanged.

What changes#

  • Capacity

    Shared API
    Shared with every customer
    Dedicated
    Reserved for your workspace on our own GPUs
  • Rate limits

    Shared API
    Your workspace's, shared by its keys
    Dedicated
    Set for your deployment, sized to your traffic
  • Limits

    Shared API
    As on Limits
    Dedicated
    Set per deployment and published at its /v1/models: read them there, not from constants in your code
  • Price

    Shared API
    $0.042 and $0.035 per 1M input tokens
    Dedicated
    Agreed for the capacity you reserve
  • Safety check

    Shared API
    On every request
    Dedicated
    On every request, as on the shared API
Shared API and dedicated deployments compared
Shared APIDedicated
CapacityShared with every customerReserved for your workspace on our own GPUs
Rate limitsYour workspace's, shared by its keysSet for your deployment, sized to your traffic
LimitsAs on LimitsSet per deployment and published at its /v1/models: read them there, not from constants in your code
Price$0.042 and $0.035 per 1M input tokensAgreed for the capacity you reserve
Safety checkOn every requestOn every request, as on the shared API

On your premises#

DecisionNode Edge and Edge Mini are open-weight models: download them and run them on your own hardware today, under their own licence. DecisionNode and DecisionNode Flash can run on your own hardware too: on premises, at the edge, next to the cameras or the production line. We offer that for qualifying deployments under an Order Form (Terms of Service 3.8), not self-serve: talk to us about yours.

For defence and security bodies, the models run inside their own network only under the 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 may sign. Military use is banned outside it. The addendum's rules are part of the model licence. Under it you:

  • run our safety-check software beside the models, with its self-harm part always on;
  • keep the records the addendum names for 2 years, and allow the audits it sets out;
  • never use the models for what the addendum forbids in every case, whatever the contract says.

Responses carry x-decisionnode-safety wherever the check runs. A self-hosted server that runs without it sends no safety header at all, so code that reads the header should treat it as optional.

Health check#

A dedicated or on-premises deployment also answers GET /healthz, for your load balancer's readiness checks. It needs no key and costs nothing. It returns 200 once the deployment is ready to answer, and 529 with Retry-After while the models are still loading. On the shared API, check a key and your connection with GET /v1/models instead.

curl -i https://<your-deployment>/healthz

How to ask for it#

Write to hello@bynn.com with your model, your peak requests and input tokens a minute, and where it must run. We size the deployment with you.

previousVersions and retirementnextFine-tuning

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 it
  2. What stays the same
  3. What changes
  4. On your premises
  5. Health check
  6. How to ask for it