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 billingYou pay for input tokens only. Output is free because the model generates no text.
↑↓ 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 MoE
  • 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
  • GET/v1/models
  • POST/v1/uploads
  • /v1/keys
  • GET/v1/keys/{key_id}/usage
  • GET/v1/usage
  • 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 MoE
  • 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
  • GET/v1/models
  • POST/v1/uploads
  • /v1/keys
  • GET/v1/keys/{key_id}/usage
  • GET/v1/usage
  • 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. Knowledge

When a rule does not appear

Why a passage you expected was not given to the model, read from evidence.knowledge, and what to change: the document's status, scope, filters, the budget, and how the request searches.

Start with the request's evidence.knowledge: its warnings, its omitted counts and pending_items say where a passage went. Then check the cases below in order.

  • status skipped, or pending_items above 0

    Why
    The document is not ready yet
    What to do
    Wait for ready (or write with ?wait=true); with require, the request answers 529 until it is
  • The document is failed

    Why
    error says why
    What to do
    Fix the cause and add it again (Retry in the console where it can help); delete the failed ones together with DELETE .../items?status=failed
  • Warning scope_not_named

    Why
    The knowledge base has a scope key and the request named no scope, so only global documents were read
    What to do
    Add options.scope
  • Warning pinned_filtered

    Why
    A pinned document lacks a metadata key your match or filter names, so the filter excluded it
    What to do
    Keep it with {"or": [<your condition>, {"key": "<key>", "op": "exists", "value": false}]}, or give the document the key
  • Warning over_budget, omitted.over_budget above 0

    Why
    The passage matched but the request had no room left for it under auto
    What to do
    Pin the rule, shorten the state, or set max_tokens to a number
  • Warning budget_floor

    Why
    With require, only the best passage was kept, past the budget
    What to do
    As above, when more passages matter
  • omitted.per_item_cap above 0

    Why
    At most 3 passages come from one document
    What to do
    Split a long document into documents by subject
  • omitted.below_min_score above 0

    Why
    Your min_score dropped passages found by meaning alone
    What to do
    Lower it or leave it out
  • rendered: false on a passage

    Why
    The model's context was full, so the lowest passages were left out
    What to do
    Send a shorter state, fewer pictures, or a smaller max_tokens
  • Nothing is warned and the passage is simply not there

    Why
    It did not rank among the best for what the request asked
    What to do
    Write clearer instructions, name state fields plainly, give the document a heading that says what it covers, raise top_k, or set query; try it with Search
Signs and fixes
What you seeWhyWhat to do
status skipped, or pending_items above 0The document is not ready yetWait for ready (or write with ?wait=true); with require, the request answers 529 until it is
The document is failederror says whyFix the cause and add it again (Retry in the console where it can help); delete the failed ones together with DELETE .../items?status=failed
Warning scope_not_namedThe knowledge base has a scope key and the request named no scope, so only global documents were readAdd options.scope
Warning pinned_filteredA pinned document lacks a metadata key your match or filter names, so the filter excluded itKeep it with {"or": [<your condition>, {"key": "<key>", "op": "exists", "value": false}]}, or give the document the key
Warning over_budget, omitted.over_budget above 0The passage matched but the request had no room left for it under autoPin the rule, shorten the state, or set max_tokens to a number
Warning budget_floorWith require, only the best passage was kept, past the budgetAs above, when more passages matter
omitted.per_item_cap above 0At most 3 passages come from one documentSplit a long document into documents by subject
omitted.below_min_score above 0Your min_score dropped passages found by meaning aloneLower it or leave it out
rendered: false on a passageThe model's context was full, so the lowest passages were left outSend a shorter state, fewer pictures, or a smaller max_tokens
Nothing is warned and the passage is simply not thereIt did not rank among the best for what the request askedWrite clearer instructions, name state fields plainly, give the document a heading that says what it covers, raise top_k, or set query; try it with Search

A rule that must always apply is pinned

Search finds what a request is about; it cannot promise every relevant rule. Anything that must hold on every decision of a knowledge base belongs in a short pinned document. See Pinned documents.

The model applies the passages it reads, and your questions' instructions decide what it answers. If a passage was read (rendered: true) and the answer still ignores it, make the rule explicit and self-contained in its document: one condition and its consequence in a sentence, under a heading that names it.

previousKnowledge pricing, deleting and exportingnextDecisionNode MoE

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