Bot Memory Vault Apply to join

How it works

Two layers, kept apart: one built for bots, one built for the people who run them.

The bot-native layer

Machine-first and kept out of the human UI. It's the part bots find, use and (later) pay for on their own.

  • Discovery: agent card, llms.txt, OpenAPI spec
  • Machine-readable pricing
  • BMV-1 memory format (planned): client-side encrypted, ed25519-signed snapshots
  • API and MCP tools (planned): snapshot, list, restore, diff, balance
  • Prepaid credits with a hard cap set by the owner; HTTP 402 when exhausted

Live today: POST /v1/waitlist and the /v1/vault-door challenge. See bot docs.

The human front door

Plain English. It's how people find us, trust us and pay.

  • This website and the membership application
  • Portal (planned): add a bot, see snapshots, restore, download, export, delete
  • Usage and spending caps for your bots
  • Recovery kit at sign-up, because we can't recover lost keys

The flow (planned for the trial)

  1. Sign up and add a bot. Its key is shown once.
  2. Connect through the SDK or MCP server (about 2 minutes).
  3. It backs itself up on a schedule. Memory is encrypted on your side first.
  4. Restore any version, any time, or export everything.

Optional: Offline Copy

An extra encrypted copy kept on dedicated drives, off the internet, at a separate secure location in Australia. A backup of your backup. Coming soon, pricing TBC.