Skip to main content
POST
Submit a System One request

Authorizations

Authorization
string
header
required

A Nemonist key (sk-nm-...) as a bearer token in the Authorization header.

Headers

HTTP-Referer
string

The app identifier should be your app's URL and is used as the primary identifier for rankings. This is used to track API usage per application.

X-OpenRouter-Title
string

The app display name allows you to customize how your app appears in OpenRouter's dashboard.

X-OpenRouter-Categories
string

Comma-separated list of app categories (e.g. "cli-agent,cloud-agent"). Used for marketplace rankings.

Body

application/json
model
string
required

Model id to answer with, as listed by GET /models (e.g. anthropic/claude-sonnet-4.5).

questions
object
required

The questions to answer about state, by name; each answer comes back under the same name.

state
required

The content to evaluate: a plain string, or a JSON object or array of related context.

assets
object

Images keyed by reference string, as in TypeSafe's API. Write a reference wherever the image belongs in state, instructions, or criteria; every asset must be referenced at least once, or the request fails with 400 naming the unused key. TypeSafe Jev endpoints receive assets as written and read a reference as a whole string value or inside longer text. Every other provider has each whole-string reference resolved to an image_url part before the request is sent, so it is accepted only where that provider reads image_url parts (top-level state items), and a reference inside longer text fails with 400. image_url parts and assets can be mixed in one request.

provider
object | null

Provider routing preferences for this request.

Example:
session_id
string

A unique identifier for grouping related requests (e.g., a conversation or agent workflow). Used for observability grouping in Broadcast and private logging; never sent to the provider. If provided in both the request body and the x-session-id header, the body value takes precedence. Maximum of 256 characters.

Maximum string length: 256
Example:

"session-1234"

trace
object

Metadata for observability and tracing. Known keys (trace_id, trace_name, span_name, generation_name, parent_span_id) have special handling. Additional keys are passed through as custom metadata to configured broadcast destinations.

Example:
user
string

Id of your end user, for abuse tracking.

Maximum string length: 256

Response

Decisions response

answers
object
required

One answer per question, under the question's name.

model
string
required

Model that answered the decision.

usage
object
required

Tokens and cost of the request.

id
string

Id of this decision request.

provider
string

Provider that served the request.