Use cases
What one key turns out to be enough for
Junkt does very little on purpose, so the interesting part is what people build with it. These are the patterns that keep coming up, each with the exact tool calls and something you can paste at your agent.
-
Stop a scheduled task running twice
A scheduled agent wakes up with no memory of ever having run. One key, checked at the top, is the difference between one digest a day and two.
get_value set_value -
Cooldowns and rate-limit windows
A key with a TTL is a lock that releases itself. No timestamp arithmetic for the model to get wrong, and nothing left behind when the window passes.
set_value get_value -
Counting across concurrent runs
Read, add one, write back is a race that silently loses counts. One atomic operation is not.
increment -
Resume where the last run stopped
Inbox cursors, last-seen IDs, pagination tokens. The small piece of context that turns a job which reprocesses everything into one that picks up where it left off.
get_value set_value -
Two agents agreeing on one fact
A scheduled job and a chat session are different conversations with no way to talk to each other, until they share a keyspace.
list_keys get_value set_value -
Pausing a running agent
The other direction: a setting you write and your agent can only read. Stop a scheduled job, or change how cautious it is, without touching its prompt.
list_controls
Give your agent a memory
Junkt is a hosted key/value store your agents reach over MCP. Free tier, 25 keys, no card, and about ten minutes from signup to a working tool call.