Key Value Pair Storage

KVdb holds simple key and value pairs that any project can read or write over a basic API, without a full database setup of its own. A Beam agent writes a value under an agreed key whenever a workflow elsewhere produces something worth storing, such as a status flag or a small cached result. Where the connector and account permissions allow it, the agent also reads keys back on request and updates them as the value changes over time. Writes that would overwrite a key holding unexpected data, or requests for a key that doesn't exist, are routed to a human to check before proceeding.

API Key Access Scope

Access to a KVdb store is scoped to the API key generated for it, so only workflows holding that key can read or write its values. A Beam agent uses the key assigned to its account and only reaches the store that key was issued for, never a broader set of data elsewhere. Where the connector allows it, the agent reads or updates values within that scope as workflows require, without needing wider access than it was given. Any request that would need a different store's key, or a permission the current key doesn't cover, is routed to a human to approve first.

Expiring Key Entries

KVdb entries can be set to expire after a period, useful for values that should only matter for a limited time, such as a temporary status or a short lived cache. A Beam agent checks whether a key it depends on is still active before relying on it, since an expired entry behaves as if it were never written at all. Where the connector and account permissions allow it, the agent refreshes an entry that a workflow still needs before it lapses on schedule. Entries that expire unexpectedly, or that a workflow assumed would persist longer, are routed to a human to investigate.