Danger zone

Docs System Zero Danger zone Updated 2026-10-27

View as Markdown

experimental, not stable

In the zone

Class: 1M context window (Danger zone). Opt in now. Requests are served once the 1M pool opens; until then they are not billed.

1M calls are stateless and are not served from cache, so all 1M input is billed at USD 0.87 per million tokens.

Opt in

Open Settings and find Danger zone. Read the release disclosures before enabling workspace access.

Enable Danger zone for this workspace.

Send SZ-Danger-Zone: accept on each request. The header name is case insensitive; the only valid value is the exact lowercase accept.

Use stateless POST /v1/system-zero/decide requests. A request header alone does not enable workspace access.

decide.sh

# Manual example policy: One attempt with no automatic retry.
# SDK defaults: The default is 5 retries, also the maximum, with 150 seconds per
# attempt and a 60-second total retry budget. A single wait longer than 60
# seconds raises the last error.
# Use Retry-After-Ms, or Retry-After when milliseconds are absent. The wait is
# never shorter than a random backoff floor: a random fraction of 0.5 seconds
# doubled for each attempt, capped at 8 seconds.
curl https://api.rightnowai.co/v1/system-zero/decide \
  -H "Authorization: Bearer $SYSTEM_ZERO_API_KEY" \
  -H "SZ-Danger-Zone: accept" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "system-zero",
    "state": "The blender I ordered arrived with a cracked jar.",
    "questions": {
      "damaged": {
        "type": "boolean",
        "instructions": "Did the item arrive damaged?"
      }
    }
  }'

Answers

The sz-danger-zone response header identifies the context used.

The response body is unchanged. The warning is not added to the body. Playground shows the returned classes with experimental, not stable.

Refusals

Any other header value returns HTTP 400 invalid_request with param set to SZ-Danger-Zone.

Code	HTTP status	Meaning
`long_context_not_available`	HTTP 404	This release can refuse an unavailable route or input.
`long_context_daily_budget_exhausted`	HTTP 429	The daily settled-charge limit has been reached. Retry after the next UTC midnight.
`service_unavailable`	HTTP 503	The service is temporarily unavailable. Retry after the returned delay.
`capacity_exhausted`	HTTP 429	Capacity is unavailable for this request. Retry after the returned delay.
`output_limit_exceeded`	HTTP 422	The decision exceeded its output token limit. The whole decision is refused without charge.

Billing

The opt-in changes no rate limit. Accepted decisions use the priced offer above.

Release disclosures

1M is an opt-in Danger zone feature. It is experimental, not stable. The opt-in itself is free.

Requires live billing, a paid card on file and a workspace that is not suspended.

1M access can be disabled for your workspace or for everyone. New 1M requests are refused while access is disabled.

If 1M is unavailable, the request is refused without charge. A decision that exceeds its output limit is refused in full with 422 output_limit_exceeded and is not billed. There is no output charge.

Opting in does not guarantee that 1M is available for every request.

1M calls are stateless and are not served from cache, so all 1M input is billed at USD 0.87 per million tokens. There is no question fee.

Sessions are not available for 1M. Each request must carry its full context.

Platform recovery work for accepted stateless 1M decisions is not billed. An existing billing decision is preserved. If no billing decision has been recorded and recovery cannot verify the original result, the decision's charge is waived.

The prompt-injection guard is not yet qualified for every input size; treat danger-zone answers as experimental.