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, no SDK to install.
  • POST /v1/decideAPI referenceAnswer typed questions about a state and optional images. 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.
  • ImagesConceptsSend images and text in the same request. The model reads printed and handwritten text, amounts, dates, objects and layout, and answers…
  • Pricing and billingYou pay for input tokens only. Output is free because the model generates no text.
↑↓ moveopen6 suggestions
Get API keyGet API key
DecisionNodeDecisionNde

Get started

  • Introduction
  • Quickstart
  • With coding agents
  • Examples

Concepts

  • State
  • Questions
  • Choice
  • Score
  • Truth
  • Number
  • Images
  • Confidence
  • Determinism

Models

  • DecisionNode-1.0
  • DecisionNode-1.0 Flash
  • Limits

Patterns

  • Confidence-gated routing
  • Fan-out
  • Guardrails
  • Control loopscomingcoming soon

API reference

  • POST/v1/decide
  • POST/v1/sessionscomingcoming soon
  • GET/v1/models
  • Errors
  • Rate limits

Pricing and billing

  • Pricing and billing

Policies

  • Responsible use

Migrate

  • Coming from a Jev-shaped API
  • Benchmarks
  • Pricing
  • Playground
Get API key
  • Guides
  • API reference
  • Examples
  • Playground

Get started

  • Introduction
  • Quickstart
  • With coding agents
  • Examples

Concepts

  • State
  • Questions
  • Choice
  • Score
  • Truth
  • Number
  • Images
  • Confidence
  • Determinism

Models

  • DecisionNode-1.0
  • DecisionNode-1.0 Flash
  • Limits

Patterns

  • Confidence-gated routing
  • Fan-out
  • Guardrails
  • Control loopscomingcoming soon

API reference

  • POST/v1/decide
  • POST/v1/sessionscomingcoming soon
  • GET/v1/models
  • Errors
  • Rate limits

Pricing and billing

  • Pricing and billing

Policies

  • Responsible use

Migrate

  • Coming from a Jev-shaped API
  1. docs
  2. /
  3. API reference

Rate limits

Limits are per workspace, counted in requests per second and input tokens per second. Over either one, the API answers 429 with Retry-After.

  • Requests

    Default
    40 per second
    Counted as
    Every call to /v1/decide

  • Input tokens

    Default
    100,000 per second
    Counted as
    usage.input_tokens across all requests
Default limits for a new workspace (provisional)
LimitDefaultCounted as
Requests40 per secondEvery call to /v1/decide
Input tokens100,000 per secondusage.input_tokens across all requests

Both limits are shared by every key in a workspace and by both models. Your current values are on the Rate limits tab of API keys in the console.

When you hit a limit#

The API answers 429 with a Retry-After header in seconds. 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: 2x-request-id: req_01J9Z6Q8T4content-type: application/json{"detail": {"error_type": "rate_limited", "message": "Too many requests. Retry after 2 seconds."}}

Staying under them#

  • Bound concurrency in batch jobs (see Fan-out) instead of firing everything at once.
  • Ask all questions about an input in one request: one request instead of many, and the state counted once.
  • Trim states. Tokens per second is usually the limit a backlog hits first.
  • Need a higher ceiling or reserved GPUs? Dedicated capacity is set to your traffic; ask through the console.
previousErrorsnextPricing and billing

DecisionNode is built and run by Bynn Intelligence, Inc.

  • Home
  • Playground
  • Examples
  • Console
  • Responsible use
  • Terms
  • Acceptable use
  • Privacy
  • Data processing
  • Defence addendum
  • Cookies

on this page

  1. When you hit a limit
  2. Staying under them