StateSet API Docs

NSR answers one question with a proof attached: is this action allowed, given what we know? The API is everything around that question — the facts and rules it reasons over, the decisions it returns, the outcomes you record afterwards, and the flywheel that turns those outcomes into better rules.


Base URL	`https://api.nsr.stateset.com`
Auth	`X-API-Key: nsr_…` (a `Authorization: Bearer nsr_…` header is also accepted); three billing endpoints also take an `X-Org-ID` header
Spec	`GET /api-docs/openapi.json` — the server publishes its own document, version 0.9.6

Generated from the running server’s document, which matches the engine repository at 0.9.6 exactly. The Verified Decisions page is the narrative for the thirteen decision endpoints; the MCP server exposes 36 of these operations as agent tools; the SDKs wrap them in four languages.

Where to start

Make a decision

approved, denied or refused, with the cited proof chain that produced it. A refusal is the safe answer when a premise is missing, not an error.

Teach it a rule

Rules are Horn clauses over your facts. Lint one before you commit it; dry-run a policy change against logged decisions before you ship it.

Record what happened

Honored, reversed, overridden, escalated. This is what makes reported confidence mean anything — the calibration curve is built from it.

Verify a proof yourself

A self-contained bundle — derivation, facts, rules — checked without trusting the engine that produced it.

The groups

Group	What lives there
Verified Decisions	Decide, batch, outcomes, calibration, refusal gaps, policy impact
Knowledge Base, Entities, Triples, Types, Beliefs, Constraints	The facts NSR reasons over, and the schema that governs them
Rules, NSR-L, Reasoning	The policy — authoring, linting, forward and backward chaining
NSR Machine, Machines	Long-running governed executors: the state machines an agent runs inside
Flywheel	Rules mined from decision traffic, and their promotion status
Macros, Templates, Answer, Conversations, Sessions	Turning a decision into a customer-facing reply
Ingestion, Jobs, Model, Provider Compatibility	Getting data in, and using NSR where a model provider is expected
Agents, Sandbox, Webhooks	Agents that act through NSR, and being told when something changed
Billing, Metering / Marketplace, Authentication	Keys, usage, entitlements, and the three cloud marketplaces

Neuro-Symbolic Architecture — what NSR is and why proofs matter
Verified Decisions API — the decision contract in depth, with the 0.9.4 verification changes
Agent Gate — a decision in front of every tool call
NSR Console & Billing — the operator side of the same engine

​Where to start

Make a decision

Teach it a rule

Record what happened

Verify a proof yourself

​The groups

​Related

Where to start

The groups

Related