Understand which public discovery data is safe to expose and where account-owned memory controls begin.
Public versus account-owned surfaces
Discovery data is deliberately public and contains no secrets. Everything that touches stored memory sits behind an authenticated, owner-scoped boundary.
- Public and read-only: service discovery, the MCP tool catalog, supported client list.
- Account-owned: memory content, agent attribution, deletion and export.
- Never public: tokens, token hashes, or any credential material.
Inspect the public discovery document
The discovery response is safe to fetch without any credential, which is what makes it usable for client setup.
curl https://xmemo.dev/.well-known/memory-os.json
Retrieval responses are not cached
Search and recall responses carry no-store headers, and audit logs record only whether a query or path was present rather than its content.
Cache-Control: no-store, private
Pragma: no-cache