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. API reference

Rate limits

Rate limits are your workspace's, shared by all its keys, counted in requests and input tokens a second. A key may carry its own lower limits. Over a limit, the API answers 429 with Retry-After.

on this page6 sections
  1. Ceilings per plan
  2. How they count
  3. Batches and sessions
  4. When you hit a limit
  5. When we are overloaded: 529
  6. Staying under them
  • Requests

    Default
    40 a second
    Counted
    Every call that is admitted under the limits (below), whatever the model
  • Input tokens

    Default
    100,000 a second
    Counted
    The usage.input_tokens of each answered request and of every session frame, charged once it is answered
A workspace's default limits
LimitDefaultCounted
Requests40 a secondEvery call that is admitted under the limits (below), whatever the model
Input tokens100,000 a secondThe usage.input_tokens of each answered request and of every session frame, charged once it is answered

Ceilings per plan#

Your plan sets a ceiling on these limits: the gateway applies the lower of the workspace's own limits and the plan's ceiling, in requests and in input tokens a second. The ceilings rise with the plan; an upgrade raises them at once. Over the ceiling the answer is the same 429 as below. A workspace with members and no plan serves no decisions (402 plan_required), so it has no ceiling to reach.

  • Starter

    Requests a second
    5
    Input tokens a second
    50,000
    API keys
    3
    Members
    2
  • Pro

    Requests a second
    25
    Input tokens a second
    250,000
    API keys
    10
    Members
    5
  • Business

    Requests a second
    100
    Input tokens a second
    1,000,000
    API keys
    100
    Members
    25
Each plan's ceilings a second, with its API keys and members
PlanRequests a secondInput tokens a secondAPI keysMembers
Starter550,00032
Pro25250,000105
Business1001,000,00010025

How they count#

  • Per workspace. The limits belong to the workspace, and every key in it shares them. One model or another makes no difference: there is one count.
  • Lower limits and a spend cap per key. A key can carry its own lower limits, in requests and input tokens a second, and a Decisions-only or Publishable key a daily spend cap (429 key_spend_cap_reached past it), so one device or one page cannot spend what the workspace can: see API keys.
  • Per second. Each limit is a budget for one second, a fixed window. The token limit refuses a request once the tokens already charged in the current second reach it; a request's tokens are charged after it is answered.
  • What counts: /v1/decide, /v1/uploads, opening a session and connecting its stream, and the Collections API calls, one request each. Session frames count their input tokens only. GET /v1/models is not limited. The usage routes, GET /v1/usage and GET /v1/keys/{key_id}/usage, do not count either: they have their own limit, 10 reads a second per workspace for the two together.
  • Your workspace's values are on the Rate limits tab of API keys.

Batches and sessions#

  • Batch calls: create, add, finalize, poll, results, cancel, list

    Counted as
    Requests, like every call
    Own limits
    None beyond the request rate
  • The requests inside a batch

    Counted as
    Not counted: they run when there is room
    Own limits
    10 active batches and 100,000 requests in active batches (draft, queued and running) per key; over them, 429 batch_limit_exceeded
  • Opening a session

    Counted as
    One request, and its fixed part's tokens
    Own limits
    Open sessions per key, 4 unless we set yours otherwise; over it, 429 session_limit_exceeded, "This key already holds <n> open sessions, the limit."
  • Frames on an open session

    Counted as
    Input tokens only: each frame's usage.input_tokens counts against your workspace's token rate, never its request rate
    Own limits
    Over the token rate, a frame error rate_limit_error with retry_after_ms; the socket stays open. Per frame: text or JSON of at most the session's max_frame_tokens, or one image
How batch jobs and sessions count
CallCounted asOwn limits
Batch calls: create, add, finalize, poll, results, cancel, listRequests, like every callNone beyond the request rate
The requests inside a batchNot counted: they run when there is room10 active batches and 100,000 requests in active batches (draft, queued and running) per key; over them, 429 batch_limit_exceeded
Opening a sessionOne request, and its fixed part's tokensOpen sessions per key, 4 unless we set yours otherwise; over it, 429 session_limit_exceeded, "This key already holds <n> open sessions, the limit."
Frames on an open sessionInput tokens only: each frame's usage.input_tokens counts against your workspace's token rate, never its request rateOver the token rate, a frame error rate_limit_error with retry_after_ms; the socket stays open. Per frame: text or JSON of at most the session's max_frame_tokens, or one image

When you hit a limit#

The API answers 429 with Retry-After, the wait in whole seconds, and retry-after-ms, the same wait in milliseconds: the rest of the current second, so Retry-After is 1 and retry-after-ms 1 to 1000. Wait that long and retry the same request; nothing was charged for the refused one. Retrying sooner only earns another 429.

HTTP
HTTP/1.1 429 Too Many RequestsRetry-After: 1retry-after-ms: 840x-request-id: req_3f6c1a9e0b2d4c7f8a1e5d9bcontent-type: application/json{"detail": {"error_type": "rate_limit_error", "message": "Rate limit reached. Retry after 1 s."}}

When we are overloaded: 529#

A 529 is not your limit: it means the work already waiting leaves no room to answer your request in time, and you are told at once rather than after a timeout. It carries the same two headers: usually 1 second; while a model is starting, the rest of its boot window, up to 600 seconds; 30 seconds while its servers are unhealthy; 1 to 2 seconds when our key store is busy. Wait at least that long, add jitter, and back off further if it repeats. A 529 is not billed.

Staying under them#

  • Bound concurrency when you fan out live calls (see Fan-out) instead of firing everything at once.
  • Move work nothing waits on into a batch job: its requests do not count against your limits, and they cost less than live calls.
  • Ask all questions about an input in one request: one request instead of many, and the state counted once.
  • Trim states. Input tokens a second is usually the limit a backlog hits first.
  • Give each service its own key with its own lower limits: the workspace's limits are shared, so a key's own cap keeps one service's backlog from using up the rest.
  • Need a higher ceiling or reserved GPUs? Dedicated capacity has limits set to your traffic.
previousSafety checknextSessions

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. Ceilings per plan
  2. How they count
  3. Batches and sessions
  4. When you hit a limit
  5. When we are overloaded: 529
  6. Staying under them