Decision APIs
Experimental. Start an SGLang decision worker with the required scoring configuration before running these examples.
NVIDIA Dynamo exposes two non-streaming decision APIs over one scoring pipeline. The HTTP route chooses the public contract; the registered model chooses the executor. Neither route is a chat/completions alias, and neither returns generated prose.
Choose a Contract
Use the exact model alias returned by GET /v1/models. See the Decision API Reference for supported fields, limits, and wire-format restrictions.
Call OpenAI Decisions with curl
The following examples use the Qwen/Qwen3-0.6B alias from the SGLang guide and a trusted local server without gateway authentication. For an authenticated deployment, configure the gateway’s required credentials and HTTPS endpoint for curl and the SDKs.
An illustrative SGLang response follows. These probabilities, confidence values, and input-token counts demonstrate the shape; they are not measured inference results or an accuracy claim.
Score levels are numbered from zero: Low is 0, Moderate is 1, and High is 2. The returned score is their probability-weighted average: 0 × 0.1 + 1 × 0.3 + 2 × 0.6 = 1.5. High has the largest probability (0.6), but the API returns the average (1.5), not High’s index (2). Use the distribution to select the most likely level when you need a single label.
Choice values remain typed: true and "true" are different options.
Call Jev System One with curl
Express the same questions using the System One wire contract:
The equivalent illustrative SGLang response uses named answers and probability maps:
See the answer-statistic definitions before using x_label_mass or confidence in application logic.
Use the Official OpenAI SDK
Install the recorded client versions in a separate client environment, not by replacing the inference runtime’s dependencies:
The OpenAI SDK base URL includes /v1. Set DYNAMO_DECISION_API_KEY to the gateway credential when authentication is required. For this unauthenticated local example, the client falls back to a placeholder because the SDK requires a key; this does not configure server authentication.
Answers are a union of types. Check answer.type before accessing type-specific fields. These examples return scored answers; do not interpret a refusal answer as a classification.
Use the Official Jev/TypeSafe SDK
Use the TypeSafe SDK (typesafe-sdk) to call Jev’s System One API, in the same client environment. Set the System One model explicitly to the registered alias. The TypeSafe SDK base URL is the server origin without /v1; the client supplies its own /v1/systemone path.
Interpret Usage and Failures
Use the usage-accounting reference to interpret token counts, including the unmeasured cache-write count. For a failed request, preserve its request ID and consult the errors and headers reference. This guide disables SDK retries so rejections remain visible; choose any production retry policy explicitly.
For admission limits and cache isolation, see Decision API Configuration. For compatibility tests against an existing deployment, see the official-client qualification suite. API/SDK conformance, native numerical parity, model-quality evaluation, and distributed lifecycle correctness are separate qualification gates.