A hundred keys in one request

Deploy time. Your app needs 80 config keys warmed before it takes traffic. One request: POST /api/v1/sqlite/kv/batch/set with an items array, each entry carrying its own key, value, content type, even its own TTL. The batch runs in a single transaction: either all 80 keys land or none do, so a half-hydrated cache isn't a state your system can be in.

Teardown is symmetric: batch/delete clears a customer's session keys in one atomic call. Reads too: batch/get returns up to 100 values in one round trip instead of 100. On a hosted document store this is a client-SDK feature with its own semantics to learn. Here it's three endpoints on storage you already run.