Documentation / Ren 1.1
Changelog
Track the API contract and model identifiers.
2026-11-13 — Ren 1.1 (ren-1.1.0)
- Public model Ren uses semantic versions. Pin
ren-1.1.0;ren-latestandren-previewboth resolve to it. Responses echoren-1.1.0inmodelandusage.model. GET /v1/modelslists the full ID and both aliases withrelease_date: "2026-11-13".- Unknown, shortened, and case-variant IDs return
400 unknown_model, naming all valid IDs.
2026-11-12 — API rules before go-live
- The gated number is
probability, the chosen answer's probability.pandconfidenceare removed. For true/false, the probability of true isprobabilities.true. - Status codes: JSON nesting deeper than 64 is
400; option and level counts are422; bodies over 4 MB and inputs over 2048 tokens stay413. A request that can never succeed never receives429. - Unknown fields are rejected at every level. Every response carries
X-Request-Id; errors are{code, message}and never repeat request content. - Default rate limits rise to 300 requests per minute per key and 600 per account.
429responses addretry-after-ms; decisions carryX-RateLimit-Limit,X-RateLimit-RemainingandX-RateLimit-Reset.
2026-11-12 — private-beta integration draft
The documented gateway surface includes typed choice, score, and true/false decisions; full semantic model IDs and aliases; bearer authentication; input-token usage; and server-side routing thresholds.
ren-1.1.0 is the full release identifier used in examples. Deployment and account availability must be checked through GET /v1/models. This entry records a contract milestone, not a measured model-quality improvement or a deployment announcement.
Future model changes should record the new pinned ID and any changes to input handling, primitives, calibration, or gate behavior. Recheck your thresholds before adopting a new version.