From 14fa49574059b2e4f449f432688b47bb846c634d Mon Sep 17 00:00:00 2001 From: Ray Walker Date: Mon, 15 Jun 2026 18:36:23 +1000 Subject: [PATCH] docs(saas-api): keep max-value note to client-facing contract only --- spec/saas-api.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/spec/saas-api.md b/spec/saas-api.md index 937481f..32c07ab 100644 --- a/spec/saas-api.md +++ b/spec/saas-api.md @@ -121,7 +121,7 @@ X-CacheKit-TTL: 3600 > **Migration:** The `X-TTL` header is deprecated. The server MUST accept both `X-CacheKit-TTL` and `X-TTL` during the transition period, preferring `X-CacheKit-TTL` when both are present. SDKs MUST send `X-CacheKit-TTL` only. The `X-TTL` header will be removed in protocol version 2.0 (targeted at SDK 1.0 milestone). > [!IMPORTANT] -> **Maximum value size:** A single cache value may be at most **25 MB**. Larger values are rejected with `413 Payload Too Large` — a **permanent** error: SDKs MUST NOT retry and SHOULD surface "value too large" to the caller. The backend stores values transparently across internal chunks, so this is a server-side ceiling (not the underlying storage cell limit) and MAY change; SDKs MUST treat any `413` as "value too large" regardless of the exact byte count. This is unrelated to the SDK serializer's 512 MB in-memory safety bound (see `wire-format.md`) — that bound governs what the SDK will serialize, not what the SaaS will store. +> **Maximum value size:** A single cache value may be at most **25 MB**. Larger values are rejected with `413 Payload Too Large` — a **permanent** error: SDKs MUST NOT retry and SHOULD surface "value too large" to the caller. This ceiling MAY change, so SDKs MUST treat any `413` as "value too large" regardless of the exact byte count. It is unrelated to the SDK serializer's 512 MB in-memory safety bound (see `wire-format.md`) — that bound governs what the SDK will serialize, not what the service will store. | Status | Meaning | | :---: | :--- |