Release 2026.11.14
API changes
One prompt cache per API key
On POST /v1/chat/completions and POST /v1/responses, cached prompt content is never shared between API keys. A prefix is served from the cache only to requests made with the key that sent it, so the first request of each key with a given prefix is billed at the full input price, even when another key has sent the same prefix. See Cached input.
cache_salt splits a key's cache
POST /v1/chat/completions takes an optional cache_salt: requests of one key with the same value share one cache, and requests with different values, or without one, do not. A platform that serves many users with one key can give each of them a cache of their own. The value must be a string of 1 to 128 characters without @, /, \ or NUL, or the request is refused with HTTP 400 and param: "cache_salt". The Responses API has no such parameter. See Cached input.
Reasoning effort levels
reasoning.effort (and reasoning_effort on chat completions) now works as published. none and minimal turn reasoning off: minimal used to turn it on. On a model with reasoning levels, low, medium and high (or xhigh) are now three levels, from the least reasoning to the most, where all of them used to give the highest; on a model without levels, any of them turns reasoning on. Any other value is ignored, where it used to turn reasoning on. Reasoning lists the levels of each model.
Streams that end early are billed for what you received
A stream that ends before its usage chunk, because you closed the connection or because it reached the 600-second limit, is billed for the output you received, on an estimate of its tokens; before, it was not billed. A stream that fails on our side, or that ends before any output, is still not billed. See Prices.
Legal
Legal documents version 1.2
Version 1.2 of the legal documents takes effect today and replaces version 1.1. The Legal document changelog lists what changes, in plain words and document by document:
- Sandboxes are covered by Annex 1 of the Terms of Service and Exhibit 4 of the Data Processing Agreement: what a sandbox stores and for how long, what is logged about it, and what not to put in a sandbox during the private preview.
- Processing locations are stated in general terms. Inference runs on Substrate AI's own GPUs in facilities in the European Union, and request handling in Microsoft Azure data centres in the European Union. The documents no longer name individual sites or cloud regions.
- With a Serenity Star account, your requests and their answers pass through Serenity Star's API, which authenticates and meters them.
- Request metadata is described by category. It still never includes your prompts or completions, and it is still kept for 90 days.
- The websites
serenityedge.ai, with its playground, anddocs.serenityedge.aiare both covered by the Legal notice, the Privacy Policy and the Cookie Policy.
Sandboxes
One API host and one key for inference and sandboxes
Set E2B_DOMAIN to serenityedge.ai and E2B_API_KEY to your Serenity Edge API key. The E2B SDKs then manage sandboxes through https://api.serenityedge.ai, the host and key you already use for inference, on the E2B API's paths (/sandboxes, /v2/sandboxes), which are not under /v1. See the quickstart.
Sandbox traffic goes to the sandbox domain
A sandbox's commands, files, terminal and ports go to its sandbox domain, which the API now returns with each sandbox in the domain field of the create and connect answers. The SDKs use it for you, and you do not set it. In the preview it is vlc1.serenitysandboxes.cloud. What a sandbox serves is never served under serenityedge.ai. See The sandbox domain.
Request limits of the control API
Each key may have 8 requests in flight to the sandbox control API and send it 120 requests a minute. Over either limit, the answer is 429 edge_key_request_concurrency_limit or 429 edge_key_request_rate_limit, with Retry-After. These limits are separate from those of the inference API, and from the running sandboxes and creates per minute of your account. A Serenity Edge API key whose account does not have Sandboxes enabled gets 403 edge_sandboxes_not_enabled. See Request limits and Errors.
If you set E2B_DOMAIN to the site's domain
E2B_DOMAIN=vlc1.serenitysandboxes.cloud, the setting given on 12 November, keeps working with the same key. The documented setting is now E2B_DOMAIN=serenityedge.ai: change to it when you next update your configuration. Your code does not change.
Documentation
- Models gains a Reasoning section with the effort values and the levels of each model; Pricing and limits describes the cache per key and
cache_salt; the chat completions reference addscache_saltandreasoning_effortand the six effort values; the coding agents guide no longer says thatlow,mediumandhighbehave the same. - Data residency and retention: processing locations in general terms, the edge network in the request flow, the Serenity Star route and a Sandboxes section.
- The Sandboxes pages document one API host for inference and sandboxes,
curlexamples againsthttps://api.serenityedge.ai, and ports reached on the host the SDKs give (sandbox.get_host(8080)). Sandbox network access and security gains a section on hosts and domains, Sandbox errors the codes of the control API, and the Sandboxes pages say where sandboxes run in general terms, in the European Union.