Cloudflare Kv

Workers KV is optimized for globally distributed reads — values written to KV propagate to all 200+ Cloudflare edge PoPs within ~60 seconds and are then served with sub-millisecond latency from the nearest PoP. This makes it excellent for configuration distribution, feature flags, cached API responses, and any read-heavy globally-accessed data. Workers binding: env.MY_KV.get("key") inside a Cloudflare Worker — zero-latency edge reads. REST API enables writes and reads from outside Workers. For agents: use Workers KV to distribute configuration or state that needs global low-latency reads; avoid for data requiring strong consistency (use Durable Objects or D1 instead). Free tier (100k reads/day) covers significant dev/test volume. Confidence is docs-derived.

REST API at api.cloudflare.com/client/v4/accounts/{account_id}/storage/kv/namespaces/{namespace_id}. GET /values/{key} reads a value. PUT /values/{key} writes a value (body: value bytes; params: expiration, expiration_ttl). DELETE /values/{key} deletes a key. GET /keys lists keys in namespace (params: prefix, limit, cursor for pagination). POST /bulk writes multiple key-value pairs in one request (array of {key, value, expiration_ttl}). DELETE /bulk deletes multiple keys. Workers binding: const value = await env.NAMESPACE.get("key", "json"); await env.NAMESPACE.put("key", JSON.stringify(data)); await env.NAMESPACE.delete("key");. Value types: text, json, arrayBuffer, stream.

REST API: Authorization: Bearer {api_token} + X-Auth-Email: {email} (or API token only if scoped correctly). Tokens from Cloudflare Dashboard → My Profile → API Tokens (scope: Workers KV Storage: Edit). Account ID + namespace ID in URL path. Workers binding: automatically authenticated via Workers runtime — no explicit auth in Worker code. HTTPS enforced. Namespace isolation provides logical separation between KV stores.

Eventually consistent: writes confirmed immediately by API, but global propagation takes up to 60 seconds. Read-after-write consistency within same Cloudflare datacenter may be immediate — not guaranteed globally. TTL support: keys can expire automatically (expiration_ttl in seconds). Value size limit: 25MB per value. Key limit: 512 bytes. Rate limiting: writes are the bottleneck (Workers KV is read-optimized); avoid high-frequency writes to the same key. REST API: standard HTTP status codes with JSON error bodies ({success, errors, result}). Workers KV uptime tied to Cloudflare global network (99.99%+ historically).

developers.cloudflare.com/kv covers Workers binding usage, REST API reference, namespace management, and key expiration. Getting started: create Cloudflare account (free), create KV namespace in Dashboard or via Wrangler CLI, bind to a Worker or access via REST in under 10 minutes. Wrangler CLI (wrangler kv key put/get/delete) for local development and scripting. Workers KV Playground in Cloudflare Dashboard. Community via Cloudflare Discord (Workers KV channel) and Cloudflare Community Forums.