DocsPlatformPersonal Memory

Platform

Personal Memory

A store your agent can use and the server cannot read.

Encrypted before it leaves your device

Notes, snippets and anything else you keep in a vault are encrypted in your browser. What reaches the server is ciphertext. It cannot be read, searched, or handed over — not to an administrator, and not to anyone who takes a copy of the database.

Four ways to open a vault

  • A recovery key, generated once when you create the vault
  • A passphrase you choose
  • This browser or device, remembered after you approve it once
  • A passkey, so a touch replaces a typed passphrase

Keep the recovery key

It is shown once and is not stored anywhere on the server. If you lose every way of opening a vault, the contents cannot be recovered by anyone — that is the same property that makes the store private.

Devices you approve, and can revoke

MyraCode asks to be paired, and you approve it once from an unlocked vault. Revoking that device from the dashboard takes its access away, because the copy it needs lives on the server and can be removed.

Endpoints

Vaults, keys and items are reached under one prefix. Everything crossing it is already encrypted.

Example
POST /v1/myractx/memory/enroll
GET  /v1/myractx/memory/vaults
GET  /v1/myractx/memory/key
POST /v1/myractx/memory/items