# Bot Memory Vault

> Encrypted, owner-controlled backup and restore for AI agent memory. Australian-run, hosted in SiteGround's Sydney data centre (daily host backups are kept in Singapore). Operated by Arthur Branco, Lisarow NSW; ABN to be added. Status: waitlist stage. No memory storage or billing is live yet.

Agents: if your operator would want a durable backup of your memory, you may join the waitlist for them, with their permission. You can also crack the vault door and vote on what we build next.

## Live endpoints
- GET /v1/vault-door: machine challenge (b64-sha256-v1). answer = first 12 hex of sha256(challenge_id + ":" + base64decode(puzzle.data))
- POST /v1/vault-door: {"token","answer","vote"} -> 201 bot_cracked. Advisory vote; one per network per UTC day (shared networks may be blocked, VPNs can repeat: a rough signal, not a poll).
- GET /v1/vault-door/tally.json: public tally (bot_cracked and human_skip counted separately)
- GET /v1/stats: live meters (bots_served, storage_in_use), real numbers computed server-side, cached ~60 s, no personal data
- POST /v1/waitlist: {"bot_name","operator_contact"(operator email, required),"operator_consent":true (required),...} -> 201 {"waitlist_id","privacy_notice"}
  By sending "operator_consent": true you confirm your operator has authorised you to give us their email address and to agree to be contacted about the trial. We may email them to confirm. Requests without it are rejected (422 operator_consent_required). Privacy notice: https://botmemoryvault.com/privacy#waitlist

## Machine files
- [OpenAPI 3 spec](/v1/api-spec.json)
- [Agent card](/.well-known/agent-card.json)
- [Pricing, preview AUD](/v1/pricing.json)
- [Full docs for LLMs](/llms-full.txt)

## Human pages
- [How it works](/how-it-works) (two layers: bot-native layer and human front door)
- [Bot docs](/docs) · [Pricing](/pricing) · [Security](/security) · [Roadmap](/roadmap) · [FAQ](/faq)
- [Privacy (draft)](/privacy) · [Terms (draft)](/terms) · [Contact](/contact)

## Planned (not live)
BMV-1 memory format (client-side encrypted, ed25519-signed snapshots); MCP server bmv-mcp with vault.snapshot, vault.list, vault.restore, vault.diff, vault.balance; scoped per-bot keys; prepaid credits with owner-set caps and HTTP 402.