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. Get started

MCP server

The DecisionNode docs are an MCP server at https://decisionnode.com/mcphttps://decisionnode.com/mcp. Connect your coding agent and it can search these pages and read any of them as Markdown while it writes your integration. No key and no sign-in.

on this page4 sections
  1. Connect your agent
  2. Tools
  3. Limits
  4. Without MCP

Documentation only

The server reads the docs; it does not make decisions. Your code makes them with the API, POST https://api.decisionnode.com/v1/decide and a key, as in the Quickstart.

Connect your agent#

The address is https://decisionnode.com/mcphttps://decisionnode.com/mcp, over Streamable HTTP. Add it once and the agent finds the two tools on its own. The name decisionnode-docs is yours to change.

Claude Code
claude mcp add --transport http decisionnode-docs https://decisionnode.com/mcp
Cursor: .cursor/mcp.json in the project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "decisionnode-docs": { "url": "https://decisionnode.com/mcp" }
  }
}
VS Code: .vscode/mcp.json
{
  "servers": {
    "decisionnode-docs": {
      "type": "http",
      "url": "https://decisionnode.com/mcp"
    }
  }
}
Codex
codex mcp add decisionnode-docs --url https://decisionnode.com/mcp

In Claude Desktop and on claude.ai, add it as a custom connector: Customize, Connectors, Add custom connector, then paste https://decisionnode.com/mcphttps://decisionnode.com/mcp and choose no sign-in. Any other client that speaks Streamable HTTP takes the same address.

Tools#

  • search_docs

    What it does
    Searches every page and heading, the same search as the docs' own. Returns up to 20 hits (8 by default), each with its page, heading, section, URL, a snippet and the path to read
  • read_doc

    What it does
    Returns one page as Markdown: the title, the lead, every section, the code samples and the tables. Takes a path from a search hit, a slug such as api/errors or a URL on decisionnode.com. An unknown path is a tool error that names the closest pages
What the server offers
ToolWhat it does
search_docsSearches every page and heading, the same search as the docs' own. Returns up to 20 hits (8 by default), each with its page, heading, section, URL, a snippet and the path to read
read_docReturns one page as Markdown: the title, the lead, every section, the code samples and the tables. Takes a path from a search hit, a slug such as api/errors or a URL on decisionnode.com. An unknown path is a tool error that names the closest pages

search_docs

querystringrequired
What to look for, 1 to 200 characters. Every word must appear in a hit; a longer word may be one typo away from a title word.
limitintegerdefault 8
How many hits to return, 1 to 20.

read_doc

pathstringrequired
/docs/api/decide, api/decide or https://decisionnode.com/docs/api/decide#retryinghttps://decisionnode.com/docs/api/decide#retrying. The #fragment is ignored: the whole page comes back.

Both tools only read, and the same call gives the same answer until the docs change. What they return is what these pages say, from the same source, so the server and the site never disagree.

Limits#

120 requests a minute per client address, and a request body of at most 64 KB. Over the rate, the server answers 429 with Retry-After in seconds; wait that long and send the call again. The server is stateless: every call is a POST, there is no session to keep and no stream to open.

Without MCP#

An agent that can fetch URLs reads the same docs from /llms.txt, a map of every page, and /llms-full.txt, every page in full. The prompt in With coding agents carries the API contract in one block.

previousWith coding agentsnextExamples

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. Connect your agent
  2. Tools
  3. Limits
  4. Without MCP