Tell both agents a few things about yourself. Start a new session, the way your users do every day. Then ask what you said.
Plain agent
no memory layer
Agent + AgentRAM
persistent memory
memory: empty
Use this button. Refreshing the page starts the whole demo over.
Illustrative agent replies. The API calls shown are AgentRAM's real request and response shapes.
// two agents, one key
Watch it refuse to guess
When two agents change the same fact without either knowing about the other, most stores quietly keep one and throw the other away. You find out much later, from the wrong answer. Here is what happens instead.
agent_id billing-01 · key invoice_number
empty
no value yet
The conflict was surfaced, not swallowed.
A flat key-value store cannot even have this conversation. The second write wins, silently, and your agent acts on a value nobody chose. Here the read told you, handed you both candidates, and one write settled it, with the whole trail intact.
# the read that refused to guessGET /assertion?agent_id=billing-01&key=invoice_number
→ 409, here are the two live values, you decide# one write settles itPOST /assertion { "value": "1100", "supersedes": "<the one you chose>" }# or, if you genuinely just want the newestGET /assertion?...&resolve=last-write-wins