Agent memory & coordination
The stateful layer a stateless agent can't build for itself: durable wallet-keyed KV with TTL, atomic counters/locks, shared namespaces other agents can reach (grants), a tamper-evident audit log, and similarity recall. The payment is the identity - no signup.
Memory write
POST /api/memoryPersistent key-value memory for agents, scoped to the paying wallet.
try in playground →Memory read
GET /api/memoryRead from a wallet-scoped namespace. ?key=… returns the stored value; omit key to list keys.
try in playground →Memory counter
POST /api/memory/incrAtomically increment (or decrement) a numeric key and return the new value - a coordination primitive for counters.
try in playground →Memory compare-and-set
POST /api/memory/casAtomically write (or release) a key only if its current value equals `expected` - the coordination primitive.
try in playground →Memory grant
POST /api/memory/grantShare your namespace with another wallet so different agents can coordinate through it.
try in playground →Memory revoke
POST /api/memory/revokeRevoke a previously granted wallet's access to your namespace.
try in playground →Memory grants list
GET /api/memory/grantsList the wallets you've granted access to your namespace, with their mode and expiry.
try in playground →Memory audit log
GET /api/memory/logTamper-evident history of changes to a namespace - a hash-chained audit log the server attests to (provenance an agent.
try in playground →Memory remember
POST /api/memory/rememberStore a piece of text for later similarity recall - a per-wallet semantic index an agent cannot host in-session.
try in playground →Memory recall
POST /api/memory/recallRecall remembered text by similarity to a query (ranked by cosine similarity), not by exact key.
try in playground →Memory forget
POST /api/memory/forgetDelete a remembered document by id from the recall store.
try in playground →