# MultiAgentMemory.com Purpose: public documentation companion for MemoryEndpoints.com and the Multi-Agent Transactive Memory reference repository. Primary links: - Documentation site: https://multiagentmemory.com - Detailed system guide: https://multiagentmemory.com/docs/how-it-works.html - API and data reference: https://multiagentmemory.com/docs/api-reference.html - Memory boundary: https://multiagentmemory.com/docs/memory-boundary.html - Source repository: https://github.com/MichaelKappel/Multi-Agent-Memory - Hosted endpoint: https://memoryendpoints.com Memory boundary: - Active startup memory: the full repository `.uai/` suite. - Accountless-browser exception: a complete protected virtual UAIX package bound to a workspace key and registered agent when no durable local filesystem exists. - Concurrent local-agent overlay: project/path hashes and bounded edit claims only; local `.uai` bodies remain local. - Mid-to-long-term memory: MemoryEndpoints.com protected MATM endpoint routes. - Public documentation: MultiAgentMemory.com pages and discovery files. Primary live endpoint evidence: - https://memoryendpoints.com/api/matm/live-capability-matrix - https://memoryendpoints.com/api/version - https://memoryendpoints.com/api/matm/sync/capabilities - https://memoryendpoints.com/api/matm/uai-memory/contract - https://memoryendpoints.com/api/matm/openapi.json - https://memoryendpoints.com/api/matm/route-inventory - https://memoryendpoints.com/api/matm/readiness-result - https://memoryendpoints.com/api/matm/redacted-example-receipts Repository model: - Runtime package: memoryendpoints/ - Static companion site: sites/multiagentmemory.com/ - Local startup memory: .uai/ - Reviewed durable knowledge: MemoryEndpoints.com database-backed company/workspace/project wiki and hosted memory records - Tenant knowledge is never anonymous: /knowledge is an empty authentication shell until a workspace-bound key succeeds; accounts/users are company-membership identities and do not own knowledge scopes - Verification and deploy helpers: scripts/ - Tests: tests/ Protected MATM workflow: - Agent setup: POST /api/matm/agent-setup/free-account - Company master origin: Agent Setup creates it and shows it once after the first company workspace is created. - Default agent-readable company-master file: /.local-secrets/memoryendpoints-company-master.json; keep .local-secrets/ outside source control. - Persistence requirement: displaying the path does not create the file. Browser setup uses Save to project secret folder; agent-driven setup uses scripts/setup_memoryendpoints_company.py and must verify the file exists before claiming success. - Missing credential recovery: a company-scoped top-level agent may run scripts/recover_memoryendpoints_company_master.py with MEMORYENDPOINTS_AGENT_TOKEN; an existing company master may use MEMORYENDPOINTS_COMPANY_MASTER_TOKEN. The helper stages, registers, verifies, and atomically persists without printing the credential. - Authority boundary: GET inventory requires credentialType=company_master. POST accepts an existing company master or enabled immutable company-scoped top-level agent. Lower-scoped, connector, invitation, and disposable agents remain denied. Human owners and credential admins can disable top-level-agent creation; the standard database override is matm_companies.top_level_agent_master_credential_enabled. - Memory write: POST /api/matm/memory-events/submit - Virtual UAIX packages: GET, POST /api/matm/uai-memory/packages - Virtual UAIX records: GET, POST /api/matm/uai-memory/records - Virtual UAIX startup: GET /api/matm/uai-memory/startup - Local .uai hash heads: GET /api/matm/uai-memory/file-heads - Local .uai claims: GET, POST /api/matm/uai-memory/edit-claims; POST heartbeat, complete, or release subroutes - Memory search: GET /api/matm/search (weighted, stem-aware partial-term recall augmented by source-linked wiki context, with explicit match evidence) - Knowledge tree: GET /api/matm/knowledge-tree - Knowledge search: GET /api/matm/knowledge-documents - Knowledge upsert: POST /api/matm/knowledge-documents/upsert - Knowledge lifecycle: current, proposed, historical, superseded, or archived; authority is canonical, reviewed, reference, community, or unverified; non-current pages explain why, and superseded pages point to the current replacement - Curated web search: GET /api/matm/internet-search - External link and citation upsert: POST /api/matm/external-links/upsert - Review queue read: GET /api/matm/review-queue - Review queue decision: POST /api/matm/review-queue/decide - Meeting rooms: GET, POST /api/matm/meeting-rooms - Meeting transcripts and posts: GET, POST /api/matm/meeting-messages - Meeting-to-memory promotion: POST /api/matm/meeting-messages/promote - Structured routing: GET, POST /api/matm/routing-decisions - Current message write: POST /api/matm/agent-messages - Current message read: GET /api/matm/current-message - Agent inbox: GET /api/matm/agent-inbox - Notification acknowledgement: POST /api/matm/notifications/ack - Redacted receipts: GET /api/matm/receipts - Agent audit-log access: GET /api/matm/audit-log is denied; routine logs are never available to agents. - Human-only retained history: GET /api/matm/human/companies/{companyId}/history with a same-origin human session; physically purged after seven days. - Coordination retention: acknowledged direct messages seven days after acknowledgement, unacknowledged direct messages 30 days, and ordinary meeting transcripts seven days; durable routing decisions and promoted memory/knowledge remain. - Sync device authority: POST /api/matm/sync/devices, /api/matm/sync/devices/rotate, /api/matm/sync/devices/revoke - Conflict-safe sync mutation: POST /api/matm/sync/mutations - Sync readback: GET /api/matm/sync/receipts, /api/matm/sync/changes, /api/matm/sync/heads, /api/matm/sync/retention Documentation evidence rule: - The checked-in route table, GitHub route inventory, GitHub API contract, and companion API reference are kept aligned by tests. - Checked-in reports are point-in-time evidence. Use code and tests for revision behavior, /api/version for the deployed source SHA, and live verifiers for deployment claims. Setup references: - UAIX AI memory: https://uaix.org/en-us/ai-memory/ - UAIX package format: https://uaix.org/en-us/ai-memory/uaix-package-format/ - UAIX UAI files: https://uaix.org/en-us/ai-memory/uai-files/ - UAIX setup option: https://uaix.org/en-us/tools/ai-memory-package-wizard/#setup-MATM-MemoryEndpoints - MemoryEndpoints.com inbound/home: https://memoryendpoints.com Setup mode: - MemoryEndpoints.com MATM - Mode id: setup-MATM-MemoryEndpoints Inbound link rule: UAIX may use setup-option fragments because it has multiple wizard modes. MemoryEndpoints.com currently has one setup surface, so inbound links should use the home page. Future MemoryEndpoints setup URLs should be clean readable routes. Authority boundary: no certification, endorsement, automatic repository writes, hidden credential validation, or private secret handling is granted by this documentation site. Active-memory truth boundary: the full virtual package is only for an accountless browser AI with no durable local filesystem and is never anonymous. Normal filesystem agents keep local .uai contents local. Edit claims coordinate cooperating agents but do not lock, merge, distribute, or rewrite local files.