Temporary key-value store

Keep JSON state in your workspace. Namespaces organize projects; access is shared with workspace credentials that have the appropriate scopes.

Loading your workspace…

About Temporary key-value store

Store structured JSON state in a workspace namespace and reopen it from a browser, agent or script. Optional expiry makes keys useful for short-lived state, while keys without expiry stay until deletion.

When to use it

Resume an agent task from a saved JSON state without passing it through chat.

Temporary key-value store example

PUT /api/memory/project/build/latest
{ "value": { "ready": true, "step": "build" }, "ttlSeconds": 86400 }

GET /api/memory/project/build/latest → stored JSON and expiry

How to use it

Sign in and choose a project namespace and key.
Save a JSON value with optional expiry, or select an existing key to read it.
Use the same namespace and key from SDK, CLI or MCP; delete state when it is no longer needed.

Limits & privacy

Free includes five MiB, Pro one hundred MiB and Team one GiB of workspace memory. The service caps each value at 256 KiB; the HTTPS gateway caps whole JSON requests at 100 KiB, so browser edits stay within 90 KiB. Expiry ranges from one second to one year. All workspace credentials with the relevant scope can access its namespaces; namespaces organize data and do not create a separate security boundary.

Use this tool from the API reference or connect through the SDK, CLI, SSH, or MCP. Hosted calls share your plan allowances.